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

The description adds a prerequisite (offer must already come from search_offers) that annotations cannot express, which is useful. However, for a non-read-only, non-idempotent operation it says nothing about whether repeated calls mint duplicate links, whether links expire, or any rate limits — the annotations only say it is non-destructive and not open-world.

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 short sentences, all earning their place: purpose with scope first, then the when-to-use condition, then the parameter contract. No filler or redundancy.

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?

For a four-parameter tool with full schema coverage and no output schema, the description covers what it does, when, and which inputs to pass. The remaining gap is minor: it never indicates what the returned link looks like or whether it is reusable, which an agent may need to chain follow-up calls.

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 description coverage is 100%, so both required parameters are already documented in the schema. The description restates the key constraints (offer_id from search_offers, full URL on the same site) but adds no new semantics such as accepted URL formats or what happens if the URL's site does not match the offer.

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 tracked affiliate link") plus the target scope (a specific page — product, category, search results — on an offer's site). It names the sibling it depends on (search_offers) and clearly separates itself from discovery tools like search_offers/get_offer.

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?

"Use it when you know the exact page that answers the user's need" gives an explicit positive trigger and implicitly excludes the explore-then-decide case. It does not explicitly name the fallback (search_offers) for when the page is unknown, but the prerequisite phrasing makes the boundary clear enough.

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