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

Annotations already cover read-only/idempotent, but the description goes further: it names the upstream data source (the Legislature's own bill-tracking service), states sort order (most recent first), states that a bill with no amendments returns an empty list rather than an error, and notes it is keyless. These are exactly the operational facts an agent cannot get from annotations.

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 verb+resource and the returned fields, then short scoping sentences. It stays dense but every clause carries a distinct fact; the enumeration of returned fields makes the lead sentence long, which is the only mild cost.

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 does the work of describing the return payload (amendment number, sponsor, type, description, floor action and date, text links, count by floor action, ordering). Combined with the empty-result behavior and data provenance, nothing needed to call or interpret this tool is missing.

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 coverage is 100% and both parameters already document accepted formats ("HB 1002", "SB 5016", bare "1002"; biennium omission defaults to current). The description adds no format or default guidance beyond the schema, so baseline 3 is correct.

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 names a specific verb and resource ("List the AMENDMENTS proposed to a Washington State legislative bill") and enumerates the returned fields, so an agent knows exactly what it gets. The closing pointer to wa_bill_status separates it cleanly from the status sibling.

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?

It gives concrete trigger phrasings ("what amendments have been offered to HB 1002", "was the striker amendment adopted on SB 5016") and an explicit alternative plus condition ("For the bill's overall status use wa_bill_status"). Nothing about when to select this tool is left to inference.

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