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

Annotations already declare readOnly, idempotent, non-destructive, openWorld, so the safety profile is covered; the description adds real value on top by naming the data provenance (federal campaign finance filings) and the derived flagging behavior for sitting members of Congress. It stops short of disclosing pagination/truncation behavior relative to the limit parameter.

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 a colon-delimited inventory of what the tool returns, plus a short compliance note. Every clause contributes content; there is no filler or restatement of the title.

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 an output schema present, the description need not explain return shapes, and it already enumerates the categories of data returned and their source. Moderate gap: it never states the default time window or result cap despite those parameters driving the scope of a filing-based list.

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 all three parameters are documented in the schema, and the description adds nothing about days, limit, or how the ticker maps to a PAC. The schema's own descriptions are terse numeric ranges ('1 to 1095'), but with full coverage the baseline of 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?

The description names a specific resource (a company's employee PAC political contributions from federal campaign finance filings) and itemizes the returned content: totals, refunds, top recipients, individual contributions, and a sitting-Congress flag. That is far more specific than the bare name and clearly separates it from siblings like list_congress_trades or list_corporate_lobbying.

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?

There is no statement of when to choose this tool over list_corporate_lobbying, list_congress_holdings, or get_company_brief, and no prerequisites or exclusions. The trailing line 'Facts, not investment advice' is a disclaimer rather than usage guidance, so an agent must infer the selection context from the ticker parameter alone.

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