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

No annotations are provided, so the description carries the behavioral burden. It states the output is JSON and requires a results link/token, but doesn't disclose whether the fetch is read-only, whether it requires authentication, rate limits, or what happens if the token is invalid or the order isn't yet finished. These are moderate gaps for a fetch tool with no 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?

A single, well-structured sentence that front-loads the action and output format. No filler words; every phrase 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?

Without annotations and without an output schema, the description is somewhat sparse. It covers the main purpose and when to use it, but lacks behavioral details like error handling, authentication, or whether the fetch is read-only. For a fetch tool with a single parameter, it is minimally adequate but leaves gaps.

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 the parameter's meaning (a URL or token) is already fully described in the schema. The description adds no further detail about the link parameter beyond what the schema provides. Baseline 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?

Specific verb ('Fetch') plus resource ('a finished Signal Leads order as JSON') and a clear output format. The description distinguishes it from siblings: signal_leads_offer and usage_and_upgrade are not about retrieving order results.

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?

Provides clear context for when to use the tool: given the results link or token from the buyer's thank-you page or email. It doesn't explicitly mention alternatives or what to do if the order isn't finished, but the condition is well-scoped.

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