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

Annotations already declare readOnly, idempotent, open-world, and non-destructive behavior, so safety is covered. The description usefully enumerates the returned payload (compensating for the absent output schema) but says nothing about auth requirements beyond the api_key parameter or any rate 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?

Three short sentences, front-loaded with the content fields the caller receives before the workflow hint and pagination note. Nearly every clause carries information; "vote actions" is slightly loose phrasing but not padding.

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 read-only tool with no output schema, the description's enumeration of returned fields is the key compensation an agent needs. Combined with annotations covering safety, the only real gap is the lack of explicit differentiation from search_information.

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 record_id and api_key are fully documented in the schema itself, including the rec_ pattern and the search_information/publish_information provenance of record_id. The description adds no parameter-level detail, 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?

States a concrete read operation and enumerates what it returns: content, review_policy, version, vote actions, and latest contributions. An agent understands this fetches a record's assessment-relevant material, though it never explicitly contrasts itself with search_information or read_vote_history.

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?

"Examine sources, then choose your assessment" implies usage in the credibility-review workflow, and "Paginate with list_contributions" routes one edge case to a sibling. There is no explicit when-to-use-this-vs-search_information guidance or statement of prerequisites.

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