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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, which covers safety. The description adds the important caveat that totals do not show current holdings or intent, which is valuable context. It doesn't disclose pagination behavior or that data represents reported (potentially delayed) transactions.

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, both informative and waste-free. The first sentence states the core function; the second adds an important limitation caveat. It's appropriately sized for the tool complexity.

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?

The tool has an output schema (so return format is covered) and good annotations. However, given it's an aggregation/normalization tool with 4 parameters including pagination, the description could mention that results are sorted/deduped, or note the lookback default behavior. The caveat about holdings/intent partially compensates but pagination behavior and data recency are left implicit.

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 50%, and the description doesn't add anything about parameters beyond what the schema provides. The 'days' lookback, 'limit', 'cursor' pagination, and 'symbols' filter are all documented in the schema itself. With moderate coverage, the description adds no extra parameter meaning, meeting the baseline.

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 states 'Return ticker-level totals from reported United States congressional transactions' with a specific verb+resource+scope. It distinguishes the aggregate view from the sibling 'politics_us_congress_trades' tool by using 'totals' vs. individual trades. However, it doesn't explicitly name the sibling alternative or contrast them.

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 implies this is a summary/aggregate tool by using 'totals,' and the sibling name 'politics_us_congress_trades' suggests a distinction, but no explicit when-to-use/when-not-to-use guidance is given. The line 'The totals do not show current holdings or intent' adds a usage caution but no direction toward alternatives.

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