gov.congress-amendment

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

No annotations provided and the description lacks behavioral disclosures such as read-only nature, rate limits, or prerequisites; only states what the tool does without addressing side effects or safety.

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?

Two sentences, no fluff, front-loaded with purpose and a concrete usage hint; every sentence is informative and efficient.

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 seven parameters and lack of output schema or annotations, the description is too brief; it leaves many parameters undocumented and no information about return values or pagination, making it insufficient for a complete understanding.

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?

Describes only three parameters (type, congress, number) out of seven; the remaining four (limit, offset, toDate, fromDate) are not explained, and schema description coverage is 0%, so the description does not fully compensate for missing parameter documentation.

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?

Clearly states it is for US Congressional amendments lookup or list from Congress.gov, specifies the three types (hamdt, samdt, suamdt), and explains how to retrieve a single amendment with congress+type+number.

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?

Implied usage by mentioning types and the single amendment pattern, but does not explicitly state when to use this tool versus alternatives or provide context for listing vs. single lookup.

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