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

With no annotations, the description carries the full burden; 'Returns' signals a read-only, side-effect-free operation and 'in CTA's records' scopes the data source. It does not disclose the important caveat that recent windows are incomplete due to disclosure lag (that detail lives only in the schema), nor the return shape or tie-breaking behavior.

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?

A single tightly packed sentence that front-loads the resource and ranking basis before the optional filters. Every clause carries meaning and there is no filler.

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, no-annotation, no-output-schema tool, the agent still cannot tell what each returned trader entry contains (name, party, chamber, count?) or how ranking ties and short result sets are handled. Adequate to know what to call, thin on what comes back.

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 parameter docs are unusually rich, including the 45-day disclosure-lag warning. The description only echoes chamber and date-window filtering without adding syntax, defaults, or interaction details, so the schema does the heavy lifting.

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?

States a specific verb and resource ('Returns the members of Congress with the most trades') plus the ranking basis ('by trade count'), which is enough to separate it from get_top_tickers or get_member_trades by resource alone. It never names an alternative explicitly, so it stops short of full sibling differentiation.

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?

The one-sentence scope implies when the tool fits (ranking members by volume), but there is no explicit when-to-use or when-not guidance against siblings like get_member_trades, get_party_breakdown, or get_aggregate_stats. The clause about chamber and date window is a restatement of parameters rather than selection guidance.

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