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

With no annotations, the description carries the full behavioral burden, and it does disclose two meaningful traits: results are restricted to purchases (sells excluded) and are rolled up per politician rather than per trade. It says nothing about ordering, result limits, pagination, or whether the window honors trade date versus disclosure date beyond the schema's own note.

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?

It is a single dense sentence with no wasted clauses, and the key qualifiers (recorded purchase, CTA's records, last N days, aggregated per politician) are front-loaded. The one long sentence is slightly hard to parse but nothing is redundant.

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 two-parameter lookup with complete schema coverage this is close to adequate, and 'aggregated per politician' hints at the return shape. However, with no output schema the description should say what each aggregated record contains (count, value, dates), which it does not.

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%, and the schema already explains the days window, its 1-365 bounds, the 90 default, and the 45-day disclosure lag. The description's 'last N days' adds nothing beyond that, so the baseline of 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 gives a specific verb ('Get'), a precise resource ('members of Congress with a recorded purchase of a specific ticker'), and a stated output shape ('aggregated per politician'). The aggregation note implicitly separates it from trade-level siblings like get_trades_by_ticker, but no sibling is named 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?

Usage is only implied: an agent can infer you call this when you want buyers of one ticker rather than a raw trade list. There is no explicit when-to-use, when-not-to-use, or named alternative among the eleven siblings, so the agent must infer routing from the purpose sentence alone.

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