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

With no annotations, the description carries the full burden and delivers: link is single-use, expires in five minutes, requires an API key in a specific header format, sha256 verification, one download per order, final on-chain payment with no refunds. It also adds prompt-injection and file-execution safety guidance, which is exactly the kind of context annotations could never provide.

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-loads the core action before the caveats, and nearly every sentence earns its place. It runs long, and the payment-finality sentence is tangential to the download itself, but it is defensible as repeat-payment prevention.

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?

No output schema exists, so the description supplies the return semantics itself: the link and its lifetime, plus the sha256 to verify against. Combined with the auth requirement, an agent has everything needed to call and interpret this tool.

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% and the single orderId is documented as 'From create_order.' The description adds no syntax or format detail beyond the schema, so the baseline of 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?

States a specific verb and resource: 'Get a one-time download link for one of your orders once it is ready.' This is clearly distinguishable from get_order_status (status) and get_asset (asset metadata) without opening any schema.

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 an explicit precondition ('once it is ready') and routes the agent to get_order_status before paying again. It does not explicitly contrast with siblings like get_asset, but the usage context is otherwise unambiguous.

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