Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already cover read-only, idempotent, and non-destructive, so the description's added value is the cost/side-effect disclaimer ('never starts, charges, or cancels') plus the provenance constraint that the batch originates from a meal-plan import and requires user confirmation. It does not say what happens when the batch is unconfirmed or expired, which would have earned a 5.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, no filler, with the scope statement front-loaded and the safety disclaimer following. Every clause carries information the agent needs.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With an output schema present and annotations covering safety, the description only needs purpose, provenance, and boundaries, all of which are present. Minor gap: no guidance on what the agent should do if the batch is not yet confirmed or the user has not acted in RecipeBee.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The single batch_id has 0% schema description coverage, so the description must carry the burden; it only implies provenance ('returned by a meal-plan import') and gives no format or lookup guidance. The UUID pattern is in the schema, but the meaning of the required identifier is left largely inferential.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Read the progress of ... an image-generation batch') and scopes it to batches 'returned by a meal-plan import'. This clearly separates it from the generate_* and get_*_image siblings that act on individual images.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly rules out starting, charging, or cancelling generation and points the agent to the user confirming the batch in RecipeBee, which is a real when-not condition. It stops short of naming the sibling tool that does start generation, so routing is implied rather than spelled out.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.