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

With no annotations provided, the description carries the full burden. It usefully discloses that closing does not process anything and that the batch is later approved by email. However, it does not explain whether the close is reversible, idempotent, or whether any state/permission requirements exist.

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?

The description is two brief sentences that pack in the action, a key behavioral caveat, and the next-step call. No filler or redundant phrasing.

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?

For a single-parameter transition tool, it covers core purpose and workflow context well. The main gap is the lack of guidance on how to obtain/format batch_ref and no mention of response behavior, but this is not severe for a simple close operation.

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?

Schema coverage is 0% and the description never mentions batch_ref, leaving the only required parameter unexplained. The name suggests it is a batch reference, but the description does not define its format, source, or relationship to the parked batch.

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?

The description opens with the imperative 'Close the parked batch', naming both the action (close) and the resource (parked batch). This clearly distinguishes it from siblings like yetty_batch_start and yetty_batch_file.

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?

It gives explicit workflow context: 'Nothing is processed yet — next call yetty_signup {email, park_ref}' tells the agent the appropriate next step after this tool. It doesn't state when not to use it or name alternatives, but the context is clear enough.

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