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

With no annotations present, the description carries the full burden and does so well: it discloses a silent failure mode (a non-matching name returns total_trades 0 with no error) and a scope limitation (only trades filed under that exact spelling are counted). These are exactly the non-obvious behaviors an agent would otherwise misread as "this member made zero trades."

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 with no filler, and the field list is front-loaded before the invocation caveats. The final sentence restates the exact-spelling constraint already covered earlier, which is mild redundancy but arguably reinforces the key failure condition.

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?

There is no output schema, and the description compensates by enumerating the returned fields, so an agent knows what it gets back without a schema. Combined with the failure-mode disclosure and the name-resolution step, nothing needed to call this correctly is missing.

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 already 100%, so the baseline would be a 3, but the description adds material meaning beyond the schema: the name is the STOCK Act filer name with honorifics stripped and is often a legal name rather than a common name, and a mismatch fails silently. That transforms a plain string parameter into one with known gotchas.

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?

Opens with a specific verb and resource ("Returns a trading profile for one member of Congress") and enumerates the exact fields returned — trade count, buys/sells, first/last trade dates, average disclosure lag, party, chamber, state, committees. This clearly separates a summary profile from the per-trade listings a sibling like get_member_trades would give, though it never names that sibling 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?

Gives a concrete prerequisite workflow — resolve the name with search_members_and_tickers before calling — and explains the consequence of skipping it. It stops short of stating when to prefer this over get_member_trades or get_committee_trading, so the routing guidance is contextual rather than exhaustive.

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