get_campaign_finance_summary

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

No annotations are provided, so the description must fully disclose behavioral traits. It mentions the tool is read-only implicitly by describing returns, but does not state data freshness, potential delays, or any side effects, which is insufficient for a tool with zero annotation coverage.

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 concise, using a standard Args/Returns format. It wastes no words, though the German language may be a minor accessibility concern. Every section is purposeful.

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 simple one-parameter tool with no output schema, the description is moderately complete: it states purpose and return elements. However, it lacks details on the format of the summary (e.g., is it a list, dictionary?) and does not address edge cases, which would improve completeness.

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 only parameter, election_year, is described in the tool's docstring but essentially repeats the schema (default value). With 0% schema description coverage, the description adds no interpretive guidance beyond what the schema already provides, failing to compensate for the gap.

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 it provides an overview of campaign finance for a year, listing specific outputs like total spending and top candidates. However, it does not differentiate from sibling tools such as get_candidate_fundraising or get_pac_spending, missing an opportunity to clarify its unique 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?

No explicit guidance on when to use this tool versus alternatives. The description implies its use for a yearly summary, but gives no conditions or exclusions, leaving an agent to infer context.

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