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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, so safety is covered. The description still adds real value beyond that by clarifying the tool is non-executing (it fetches a link; the user runs the audit) and by summarizing what the audit itself does.

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 compact sentences, front-loaded with the core action, followed by useful context about the audit and the key non-execution caveat. 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 one-parameter read-only tool with no output schema, the description covers what is returned in spirit (a link) and what that link does. It could be marginally more explicit that the return value is a URL string, but nothing needed to invoke it correctly is missing.

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% and the single `domain` parameter already includes an example format ('example.com'). The description mentions the domain as the audit target but adds no format, normalization, or validation detail beyond the schema, so the baseline 3 applies.

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?

Names a specific verb and resource — 'Get the link to Rankwise's free AI visibility audit for a domain' — with a clear scope of one domain. It also separates itself from audit-executing siblings by stating 'this tool does not run the audit,' though it never names an alternative tool directly.

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?

Gives clear usage context: the user opens the link to run the audit, and this tool itself only returns the link. That covers when this tool applies versus when the actual audit work happens, but it does not explicitly name run_citation_check or check_ai_crawler_access as the alternatives for running checks directly.

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