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

With readOnlyHint/idempotentHint/openWorldHint already declared, the bar is lower, yet the description adds real operational context: it is a static snapshot scoped to 118th-Congress HR/S, descending committee->subcommittee hierarchy is preserved with parent links and dated activities, and an empty result is a data-absence signal rather than an error. It does not discuss rate limits or auth, but for a read-only provenance tool the scoping and hierarchy semantics are the material traits.

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?

Front-loaded with the purpose and preserved fields, then the when-to-use triggers, then the coverage caveat. Three sentences, all load-bearing. Slightly dense with enumerated field lists, but nothing is redundant filler.

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 no-output-schema, read-only provenance tool, the description covers the return shape (full hierarchy path), the identity keys (stable committee codes, parent links, chambers, types), temporal data (dated activities), and the snapshot boundary plus absence semantics. An agent has everything needed to invoke and interpret it.

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 schema already documents the HR/S enum, the 118th-Congress bill_number range, and response_format. The description adds no parameter-level syntax beyond what the schema provides, and the 3-param / 100%-coverage rule sets the baseline at 3.

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: 'Return the complete committee and subcommittee path published in GovInfo Bill Status XML for one bill.' It enumerates the preserved fields (stable committee codes, parent links, chambers, types, dated activities), which is far more precise than any sibling (govinfo_legislation_relationships, govinfo_legislation_evidence_pack).

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 three explicit use-case phrasings ('which committees handled H.R. 2?', 'show subcommittee referrals for this bill', 'build a committee-routing audit trail') and boundaries: 'Coverage is 118th-Congress HR/S only; absence means the captured XML supplied no committee record.' This tells the agent both when to use it and what an empty result means.

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