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

Annotations already declare readOnlyHint and destructiveHint false, so the safety profile is covered. The description adds meaningful behavioral nuance beyond annotations: results are research leads rather than evidence, and the endpoint may return nothing if the index is empty or suggestions have been disabled.

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?

The description is two sentences with no filler. The core action is front-loaded, and the clarifying caveats each add essential information about result interpretation and empty responses.

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?

With an output schema present, the return structure is already covered. The description explains the key empty-case and interpretive caveat, but it is still missing parameter-level guidance for 'limit' and general selection guidance relative to sibling tools.

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 0%, so the description must compensate for undefined parameters. It implicitly explains that 'id' refers to a public record, but it says nothing about 'limit,' its default, or how it affects returned suggestions.

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 uses a specific verb-resource pair, 'Get the site's existing similarity suggestions for a public record,' which clearly identifies what the tool returns. It also distinguishes the operation from sibling tools like get_record and search_records by focusing on precomputed similarity suggestions.

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 description gives useful interpretive context by saying these are 'research leads, not evidence of a historical relationship,' which implies when not to rely on it. However, it does not explicitly name alternatives or give concrete conditions for choosing this tool over siblings like search_records.

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