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

With no annotations, the description carries the burden and does well: it discloses the source, the default sort order, and a meaningful latency caveat (PTRs disclosed up to ~45 days after the trade, so "recent weeks" not real-time). It does not mention result caps/pagination limits, which is the main remaining behavioral gap.

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?

Dense and front-loaded: identity/source first, returned fields second, filtering and ordering third, then the caveat last. No filler sentences; the caveat is explicitly signposted with "CAVEAT".

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?

No output schema exists, and the description compensates by enumerating the row fields (member, chamber, ticker, company, type, dollar range, dates, per-trade performance). The only omission is the limit/pagination parameter, which leaves an agent unaware of how to size result sets.

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 0%, so the description must compensate, and it does for four of the five params: ticker, member (substring semantics added), chamber, and type (purchase/sale/exchange). The limit param is never mentioned, so an agent learns nothing about result capping from the description.

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?

Specific verb+resource: returns U.S. Congress stock trades from STOCK Act PTRs (House Clerk + Senate eFD). This clearly distinguishes it from the siblings get_congress_member (member lookup) and get_congress_stats (aggregates), and the data provenance is stated up front.

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?

"Filter by ticker, member (substring), chamber, or type. Newest transaction first." gives concrete usage context, including the substring matching behavior for member. However, it never names the sibling tools or states when to prefer them over this one, so there is clear context but no explicit alternatives/exclusions.

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