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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and openWorld, so the safety profile is covered by structured data. The description adds one genuinely useful behavioral fact — 'Returns committee IDs' — which matters because there is no output schema and it signals the response is identifiers rather than full committee records. It says nothing about pagination, default/max result counts, or how ID output should be chained into another call.

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 filler, with the capability and its coverage front-loaded and the return contract placed last. Every clause carries information.

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 read-only search tool with full schema coverage and no output schema, the description covers purpose, filter dimensions and the shape of the result (IDs). Minor remaining gap: nothing about result limits or pagination behavior, which the schema only partially implies via the limit parameter.

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 all five parameters (cycle, limit, query, state, committee_type) are already documented with formats, bounds and enum codes in the schema. The description restates three of the filter dimensions (name, state, committee type) without adding syntax or semantics beyond the schema, so the baseline 3 applies.

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 (Search) and resource (FEC-registered political committees) and enumerates the subtypes covered (campaign committees, PACs, party committees, Super PACs), which is unusually concrete. It does not explicitly distinguish itself from adjacent FEC siblings such as fec_candidate_search or fec_independent_expenditures, but the resource noun is distinct enough for an agent to route correctly.

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 phrase 'by name, state, or committee type' implies how the tool is meant to be driven, which is useful implied usage guidance. However there is no statement of when to use this versus fec_candidate_search, when to add a cycle, or any exclusion — the agent must infer routing from the resource name alone.

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