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

With no annotations, the description carries the whole behavioral burden, and it does disclose two useful traits: data comes from CTA's records and results are ordered newest first. It does not disclose pagination behavior, the default cap of 50, how filing lag affects totals, or what a returned trade record contains.

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 sentence, front-loaded with the verb and resource, ending on the useful ordering detail. There is no filler and nothing an agent must read past to reach the core claim.

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 three-parameter read tool this covers the essentials, and the rich parameter schema compensates for the lack of annotations. But with no output schema, the description never indicates what a trade record looks like (member, party, chamber, amount, filed date), which an agent would need to plan follow-up calls.

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 the schema already explains the ticker format, the days look-back window with the 45-day disclosure lag caveat, and the limit cap. The description adds nothing beyond 'specific stock ticker symbol', so the baseline 3 applies.

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') plus resource ('congressional trades') and scope ('for a specific stock ticker symbol'), and it adds ordering ('newest first'). That distinguishes it from a member-centric sibling such as get_member_trades, though it never names the siblings it competes with.

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 this is the right tool when it has a ticker symbol and wants trades. There is no explicit when-not guidance, no mention of alternatives like get_ticker_buyers or get_trade_feed, and no note on prerequisites or data-source limits.

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