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

Annotations already declare readOnly=true and destructive=false, so safety is covered; the description adds non-obvious context that _meta.requires_confirmation is always true and that criteria must be surfaced for explicit user confirmation before acting. That is genuine workflow information not present in the structured fields, though it doesn't explain what happens if no criteria exist for the category.

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 short sentences, zero filler, with the primary purpose stated first and the workflow constraint second. Every clause carries actionable 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?

For a single-parameter read tool with an output schema absent, the description covers purpose, sequencing, and confirmation flow adequately. The only gap is not indicating the shape of the returned criteria or the no-criteria case, which matters since criteria drive downstream filtering.

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 single category parameter is typed only as string, so the description carries the burden and partially compensates by listing example values ('homes, cars, or any freeform name'). It does not say how unknown or case-variant categories are handled.

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?

Opens with a specific verb and resource ('Retrieve the saved buy-box criteria') and gives concrete category examples. It never names set_buy_box or delete_buy_box, so the read-vs-write distinction must be inferred from the verb, but the purpose is unmistakable.

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?

'Call this before searching or filtering' gives a clear triggering condition, and the confirmation rule tells the agent how to proceed after reading. It stops short of explicit exclusions (e.g., what to do when no buy box has been set — presumably set_buy_box), so it is not a full when/when-not/alternatives statement.

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