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

The annotation readOnlyHint=true already indicates a read-only operation, and the description does not contradict that. It adds behavioral context by stating it is a poll operation that returns data only when available ('once available' for receipt ID), implying the agent may need to retry. It does not mention error handling or rate limits, but these are minor gaps given the read-only nature.

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 sentences with no fluff. The first sentence states the purpose and return fields, the second provides the timing guidance. It is front-loaded and every sentence earns its place.

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 poll operation with no output schema, the description covers the essential information: what it returns, when to call it, and how it relates to confirm_delivery. An agent has enough context to invoke it correctly without additional documentation.

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 100% because both parameters (apiKey and orderId) have descriptions in the input schema. The tool description does not add any additional parameter-level detail beyond what the schema provides, so the baseline score of 3 is appropriate.

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 verb 'Polls' and the resource 'an order placed by this agent', and lists the specific fields returned (orderStatus, escrowStatus, funding timestamps, tracking info, receipt ID). It is distinct from siblings like cancel_order and confirm_delivery, which are actions, and get_receipt, which is a separate retrieval tool. The purpose is unambiguous and specific.

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 explicitly states when to use the tool: 'Poll after funding the deposit address, and after the seller ships, before calling confirm_delivery.' This gives clear timing and sequencing relative to other operations, and it also distinguishes from confirm_delivery by indicating it must be called before that action. This is explicit usage guidance.

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