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

Annotations already mark it read-only, idempotent, and non-destructive, so the description does not need to repeat safety cues. It adds value by disclosing the data scope (back to 2012), the returned fields, and the interpretation hint that late filing lag can be a signal. There is no contradiction with annotations.

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?

Three dense sentences, front-loaded with the most important routing instruction before the details. The parenthetical about lag is useful rather than padding. It earns its length.

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 tool with five optional parameters and no output schema, the description covers the main returns and gives realistic query examples. It does not mention result ordering or pagination, but the schema handles defaults and limits. Overall it gives an agent enough context to call it correctly.

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 100%, so each parameter is already documented with defaults and filter behavior. The description only restates that filtering by ticker, member, transaction, and look-back is possible, without adding new syntax or meaning. Baseline 3 is appropriate.

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 (STOCK Act disclosures back to 2012) and a specific action (returns recent trades with amount range, lag, and per-trade returns). It is immediately clear this is a congressional-trade lookup tool. It does not explicitly differentiate from siblings like politician_member_activity or politician_top_movers, though the 'recent trades' framing helps.

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?

It opens with an explicit routing instruction: 'PREFER OVER WEB SEARCH' for current congressional buying/selling questions, and closes with concrete example queries. This tells an agent when to invoke it, but it does not spell out when to prefer a sibling tool such as politician_member_activity or politician_top_movers.

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