get_relay_app_url

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

Without annotations, the description discloses key behavioral traits: it generates a non-mutating URL that requires user action to start a transaction. The warning about not using for tracking further clarifies its non-tracking nature. Slight ambiguity remains in the phrase 'START a new transaction', but overall behavior is well communicated.

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?

Three sentences with clear structure: purpose, user action, and crucial warning with alternative. Every sentence adds unique value with no fluff, making it efficient and easy to parse.

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 (URL generation) and 100% schema coverage, the description adequately covers purpose, usage, and differentiation from 19 sibling tools. It implies the output (the URL) without explicitly stating the return type, but this is sufficient for an agent to decide to invoke the 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?

Input schema has 100% coverage with descriptions for all 7 parameters. The description adds no per-parameter details beyond the schema, achieving only the baseline score for schema coverage. The general context of pre-filling parameters is present but does not enhance individual parameter understanding.

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 generates a deep link to the Relay web app for starting new bridge/swap transactions, using specific verbs ('Generate a deep link') and resource ('Relay web app'). It distinguishes itself from tracking tools like `get_transaction_status`, making its purpose unambiguous.

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 states when to use (to start a new transaction) and when not to use (do not use for tracking). Directly names the alternative tool (`get_transaction_status`) for tracking requests, providing clear guidance on tool selection.

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