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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the tool is safe to call. The description adds valuable behavioral context: it mentions coverage constraints (118th-Congress HR/S only), the absence behavior (no committee record in captured XML), and the preservation of stable codes and dated activities兴盛 This goes beyond the annotations and helps the agent understand what to expect in terms of data completeness.

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 long, with the core purpose and output components in the first sentence, followed by usage examples and coverage in the second. It is front-loaded with the key information and avoids unnecessary words. Every sentence adds value: the first defines what it does, the second gives usage and limitations. It is concise and well-structured.

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?

Given the tool's moderate complexity (3 parameters, 2 required, no output schema), the description covers the essential aspects: what it returns (committee path components), when to use it (examples), coverage constraints (118th Congress HR/S only), and absence behavior. The schema already handles parameter details, and annotations cover safety. There is no critical missing information for an agent to invoke this tool correctly.

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?

The schema has 100% description coverage, so parameters like bill_type, bill_number, and response_format are already well-documented in the schema. The description adds context by explaining the scope (118th Congress HR/S only) and providing usage examples, which clarifies the meaning beyond the raw schema. It doesn't add deep syntax details for each parameter, but the schema already covers that. Given high schema coverage, a score of 4 is appropriate for the added context.

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 clearly states the tool returns the complete committee and subcommittee path from GovInfo Bill Status XML for one bill, specifying the exact resource (GovInfo Bill Status XML) and the output components (committee codes, parent links, chambers, committee types, dated activities). It distinguishes itself from siblings like govinfo_legislation_relationships and govinfo_legislation_version_lineage by focusing on committee paths, and provides explicit example queries. The purpose is unambiguous and specific.

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 explicit usage examples ('which committees handled H.R. 2?', 'show subcommittee referrals for this bill', 'build a committee-routing audit trail'), which tells the agent when to use this tool. It also states coverage limitations (118th-Congress HR/S only) and the absence handling, which helps the agent decide if this tool is appropriate. Though it doesn't mention alternatives explicitly, the clear use cases and limitations suffice to guide selection.

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