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

Annotations already declare readOnly, non-destructive, closed-world, non-idempotent behavior, so the bar is lower. The description still adds real context: no search, no destination verification, free/no key/no credits/no wallet, and inherited input limits.

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?

Compact and front-loaded, with the core behavior leading. The telegraphic fragments ('FREE during validation. No key, credits or wallet.') are efficient but slightly choppy rather than fully structured.

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?

An output schema exists, so return values need not be fully spelled out, and the description does characterize the return shape anyway (URLs + matched words, not a page dump). For a read-only ranking tool with annotations covering safety, this is nearly complete.

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 67% and the nested input object is the bulk of the contract. The description only gestures at html/query/sourceUrl generically and says nothing about maxLinks, the 100k/300/2048 limits, or the ignored legacy requestId/maxPriceMicroUsd fields, so it adds little beyond the schema.

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+resource+output: rank real links in supplied HTML against a query, returning direct URLs and matched words rather than a page dump. This clearly separates it from plain extraction siblings like html_links, though it never explicitly names the near-identical agent_utilities_link_shortlist_preview.

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?

The negative framing ('No search or destination verification', 'Existing source and input limits apply') implies the scope, but there is no explicit when-to-use statement or routing to the closest alternative, agent_utilities_link_shortlist_preview. Usage is inferable but not stated.

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