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

Annotations already declare readOnlyHint=true, openWorldHint=true, idempotentHint=true, and destructiveHint=false, covering safety and non-execution. The description adds the crucial context that 'Opening it executes nothing,' reinforcing the non-executing nature. It also implies the output is a URL, adding value beyond annotations.

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 concise sentences: the first explains what the tool produces, the second clarifies when to use it. Every word earns its place, and the critical usage guideline is 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 tool's simplicity (creating a URL) and the rich schema and annotations, the description covers all essential aspects: purpose, usage context, and behavioral safety. No output schema is present, but the description adequately implies the return is a URL, which is sufficient.

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%, so all parameters are documented in the schema. The description doesn't add extra parameter-level detail, but it does clarify the overall purpose and that the tool generates a link, adding context beyond the schema. Since schema coverage is high, a 4 is justified for the added contextual value.

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's function: creating a pre-filled URL for a trade ticket, listing the exact fields (event, market, outcome, side, amount). It distinguishes itself from siblings by emphasizing it is a URL for human review, not an order execution.

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?

Explicitly says when to use it: 'when you have no wallet or need human confirmation.' This contrasts with other tools that likely execute trades (e.g., quote_order), providing clear usage boundaries.

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