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

Annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, so the safety profile is covered. The description goes beyond them with concrete behavioral rules for the agent: prompt the user for missing data, never fabricate names or dates, and follow the upload/checkout sequence.

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?

Three short sentences, front-loaded with the payload of what to collect, followed by behavioral guardrails and the next-step handoff. Every sentence carries distinct information with no filler.

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 read-only, two-parameter, no-output-schema tool, the description covers what the call yields (the collection requirements plus turnaround and pricing options) and where it fits in the workflow. It stops short of describing the shape or ordering of the returned list, but nothing essential for correct invocation is missing.

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 description coverage is 100%, so the schema already documents both parameters (handle from find_posters, optional buyer_country for local prices). The description mentions prices and turnaround options, loosely echoing buyer_country's purpose, but adds no syntax or mapping detail beyond the schema, so the baseline 3 applies.

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 states a specific verb and resource: it lists exactly what must be collected from the user for one poster (names, dates, optional message, photo, turnaround options, prices). It is clearly distinguishable from siblings like find_posters or create_poster_checkout because it is framed as the requirements-gathering step that precedes them.

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 routes the agent explicitly: 'Next step: upload_photo, then create_poster_checkout,' and tells the agent to ask the user for anything unknown and not invent names or dates. That is clear context plus sequencing, though it never states a case where this tool should not be called.

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