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

Annotations already declare readOnly, idempotent, closed-world, non-destructive, so the safety profile is covered. The description adds that output is aggregated and party-split, which is genuinely useful context beyond annotations, but says nothing about pagination, result ordering, or what the sentiment value represents numerically.

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?

One front-loaded sentence with no filler. It could have used the remaining space to explain the sentiment metric or when to use it, but nothing present is wasteful.

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 no output schema, the description should clarify the shape of the aggregated result (per-ticker, per-party sentiment values and their units). It only hints at the grouping, leaving the agent unsure what a response actually contains; the absent ticker parameter compounds this.

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 seven parameters (limit, cursor, date bounds, party enum) are already documented and the baseline is 3. The description adds no parameter guidance and actually references a 'ticker' dimension that has no corresponding parameter in the schema, which mildly undermines trust.

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 ('aggregated politician trading sentiment'), plus the aggregation dimension (by ticker) and breakdown (party). This clearly separates it from trade-level siblings like get_politician_trades, though it does not name them explicitly.

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 indication of when to prefer this over get_politician_trades, get_politician_portfolio_holdings, or get_congress_ranking. The agent must infer that this is the summary/aggregate variant from the word 'aggregated' alone.

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