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

Beyond the annotations (readOnlyHint=false, idempotentHint=true, destructiveHint=false), the description discloses the real behavioural profile: it checks the Returns policy window, records the request for a human, returns a photo-upload link, and crucially 'refunds nothing' because a person decides and replies by e-mail. That is exactly the side-effect and expectation-setting context annotations cannot convey.

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?

Front-loaded with the trigger ('Use this when...') followed by the ground list, then the behaviour, then the limitation. The ground enumeration is long but each item earns its place; the second half is tight and every sentence carries information.

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 no output schema, the description correctly explains the response (a link for sending photographs) and the follow-up path (human review, e-mail reply). Combined with annotations covering mutation and idempotency, an agent has enough to call this correctly; only the cancel_purchase overlap remains unaddressed.

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%, with the enum ground values and the order_token/buyer_email pairings already documented in the schema, so the baseline is 3. The description adds only a light cross-reference ('Needs the same proof as get_order_status') and the fact that grounds follow Returns §2; it does not add format or selection guidance beyond the schema.

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 ('open a claim / return a work') and enumerates the exact grounds it handles, so an agent can map a buyer complaint to this tool without opening the schema. It also distinguishes itself from siblings by name ('Needs the same proof as get_order_status'), anchoring it against the other order tools.

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?

Gives explicit, concrete when-to-use triggers (damage, non-delivery, authenticity doubt, unauthorised agent purchase, cancellation before dispatch, 30-day return) and states the outcome. It does not, however, resolve the overlap with the sibling cancel_purchase, since 'cancelling before dispatch' is listed as a ground here without saying which tool should win.

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