congress_bill_actions

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

Annotations already declare readOnlyHint=true, so the description doesn't need to restate safety. It adds the useful detail that roll-call vote numbers are shown when available, but doesn't disclose other behaviors like pagination or chronological ordering. Modest added value beyond the annotation.

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 concise sentences pack a clear purpose and a usage pointer with no filler. Every word earns its place.

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?

The description covers the tool's purpose, the types of data returned, and the prerequisite search step. Without an output schema, it could specify more about return structure, but the description is sufficiently complete for this moderately simple tool.

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 parameters are fully documented in the schema. The description only restates the need to obtain congress, bill_type, and bill_number via a search tool, adding no extra semantics beyond schema.

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 retrieves the full action history/timeline for a bill, enumerating the stages (introduction, committee, floor votes, amendments, signing). It distinguishes itself from sibling tools like congress_bill_details or congress_bill_amendments by its specific scope.

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?

Explicitly tells the agent to use congress_search_bills first to obtain required parameters (congress, bill_type, bill_number). This provides clear prerequisite context, though it doesn't explicitly contrast with alternative bill-related tools.

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