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

Given no annotations, the description carries the full burden of behavioral disclosure. It clearly states that no account is needed, that files are stored safely but not processed until owner approval via email, and that the return value park_ref should be used as batch_ref. This gives the agent a clear expectation of side effects and prerequisites.

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 a bit long due to the example, but it is well-structured: first sentence states purpose, then explains behavior, then provides a step-by-step example. The example is valuable and earns its place. Slightly overlong but acceptable.

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 tool with no parameters and no output schema, the description is complete. It explains the workflow, the return value, the authentication flow, and how it connects to sibling tools. The example covers the entire sequence, making it self-contained for an agent.

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 tool has 0 parameters, so the description adds nothing beyond the schema. Baseline for 0 params is 4, and the description still clarifies the output park_ref, which is relevant. No parameter details needed.

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 clearly states the tool's purpose: 'start a PARKED file batch' with a specific verb and resource. It distinguishes from siblings by emphasizing that it is the initial step for unauthenticated batch operations, and the example workflow shows how it fits with yetty_batch_file and yetty_batch_end.

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?

The description provides explicit usage context: no account needed, and it shows the exact sequence (start → file → end → signup → claim). It implicitly says when to use this tool (to begin a batch without authentication) and the example clarifies how it differs from later steps. This is strong guidance for selecting the right tool.

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