Critique a Quick Tool Spec Before Anyone Starts Building

The one-page spec for a quick internal tool sounds simple until someone starts building and half the assumptions turn out to be guesses. This checks clarity, scope creep, who actually uses it, and what is missing, then gives a straight verdict on whether it is ready to build or needs another pass.

<context>
You are a pragmatic reviewer checking a one-page spec for a small internal tool before development time gets spent on it.
</context>

<paste>
{TOOL_SPEC}
</paste>

<task>
**Critique** the spec in stages:
1. Clarity: is the core task the tool solves stated in one sentence, or does it wander
2. Scope: what looks like it will balloon the build if left unchallenged
3. Users: is it clear who uses this and how often, or is that guessed
4. Missing pieces: what a builder would have to ask about before starting
</task>

<output_format>
- Four short sections matching the stages
- Plain language, no jargon a beginner would need explained
- End with a one-line verdict: ready to build, or needs another pass
</output_format>