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

Annotations already declare readOnlyHint=true and destructiveHint=false, so safety is covered; the description adds real value by disclosing that members and hearings are merged into the response and clarifying what each contains (roster with roles, scheduled meetings). It says nothing about response size limits or pagination behavior beyond what the schema's max_items already encodes.

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?

A single front-loaded sentence with the required parameter, the endpoint, the optional merge behavior, and a sibling pointer — no 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 3-parameter read tool with 100% schema coverage and full annotations, this covers invocation fully. With no output schema, it could say a bit more about the returned committee shape, but nothing an agent needs to call it correctly 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%, so the baseline is 3, and the description goes beyond it by glossing 'members' as a role-bearing roster and 'hearings' as scheduled meetings, and by explaining the provenance of committee_id. It adds no further detail on max_items semantics (cap vs. default) beyond the 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?

States a specific verb and resource ('Fetch a committee by committee_id') plus the underlying endpoint GET /v1/committees/{committee_id}, and names the sibling (list_committees) that produces the identifier — clearly separable from get_legislator, list_committees and get_hearing.

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 routes the agent to list_committees to obtain a committee_id and explains when the optional include sub-resources apply. It lacks an explicit 'don't use this if you just need a list' exclusion, but the context is unambiguous.

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