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

With no annotations provided, the description must carry the full burden of behavioral disclosure. It only explains the two data types and does not mention any prerequisites (e.g., committee_id required for type=expenditures), limitations, pagination, or return format. This is insufficient for a tool with no structured behavioral hints.

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?

The description is extremely concise at two sentences, front-loading the main action ('Get campaign spending data') and then efficiently explaining the two key types. Every sentence earns its place without unnecessary elaboration, achieving high readability and structure.

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?

Despite having 5 parameters, no output schema, and no annotations, the description is brief and leaves out important context. It does not explain the parameter interactions (e.g., committee_id required for expenditures), data scope, or behavioral nuances. This makes it incomplete for an AI agent to fully understand the tool's usage and constraints.

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?

The schema already covers all parameters with descriptions (100% coverage), so the baseline is 3. The description adds minor nuance to the 'type' parameter (e.g., 'for/against candidates', 'direct campaign spending') but does not address the other parameters beyond what the schema provides. Thus, it adds marginal value only.

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's purpose as retrieving campaign spending data, with a specific verb ('Get') and resource ('campaign spending data'). It further distinguishes between two spending types ('independent' for Super PAC/outside group spending and 'expenditures' for direct campaign spending), which effectively sets it apart from sibling tools focused on candidates and donors.

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 description provides clear context on when to use each type parameter ('Type=independent for...' and 'Type=expenditures for...'), but it does not explicitly address when to choose this tool over sibling tools or mention exclusions. The guidance is implied rather than fully explicit, warranting a mid-range score.

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