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

Beyond the read-only and idempotent annotations, it discloses the sensitive nature of the order ID, that the order page shows addresses and amounts, that the response never includes those fields, and that no account or credentials are required. This is rich behavioral context directly useful to an agent.

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?

Although longer than some tool descriptions, every sentence adds distinct value: purpose, privacy warning, usage rule, return contents, explicitly excluded data, and read-only/no-auth nature. The most important purpose and privacy constraints are front-loaded.

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?

Given the single-parameter schema, abundant annotations, and available output schema, this description is complete. It explains what the tool returns, what it deliberately does not return, and how to handle the sensitive order ID, leaving no significant gap for correct invocation.

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 schema already fully documents orderId, so this dimension starts at baseline 3. The description adds meaningful guidance: the order ID is private, must be one the person gave you, and should never be repeated elsewhere. That extra semantic layer justifies above baseline.

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 checks the stage of a HiddenSwap order by order ID, with a concrete verb and resource. It enumerates possible stages, which distinguishes it from sibling tools like get_quote and search_coins that serve different purposes.

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 gives clear context: use it only when checking an order's stage using an order ID the person provided. It does not explicitly name sibling alternatives or state when not to use them, but the distinct domain makes the usage context unambiguous.

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