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

Annotations already declare readOnlyHint, idempotentHint, and openWorldHint, so the safety profile is covered. The description adds real behavioral context beyond that: the data source (GovInfo Bill Status XML), pagination, and an explicit coverage constraint ('coverage starts from 118th-Congress HR/S bills; related targets may be resolution types that are not otherwise hosted as primary records').

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 core purpose and payload contents are front-loaded in the first sentence, followed by use cases and a coverage caveat. It is dense but every clause carries information; only the enumeration of relationship types borders on verbose.

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 no output schema, the description compensates by naming the fields each relationship record returns (measures, identifier, latest action), and it discloses the congress/measure-type coverage boundary. Little is missing for correct invocation, though return shape details like ordering are not specified.

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 the schema already documents limit, offset, bill_type, bill_number, and response_format, including enum constraints. The description does not add syntax or format detail beyond what the schema provides, 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 specific verb and resource ('Return a paginated related-measure map for one bill') and enumerates exactly what the map contains: companion, identical, related, and procedurally related measures, who identified each, and the target's latest action. This clearly separates it from sibling tools like govinfo_legislation_search, _committee_path, and _version_lineage.

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 concrete triggering scenarios ('find the Senate companion to this House bill', 'which rule resolution governed this bill?', 'map CRS-identified related measures') that tell the agent exactly when this tool is the right choice. It does not explicitly name sibling alternatives or exclusions, so it falls short of a 5.

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