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

With no annotations, the description must carry the full behavioral burden. 'Returns' and 'CTA's records' imply a read-only lookup over a dataset, and the output contents are described well. However, it does not disclose that the newest part of the window may be incomplete due to disclosure lag (that caveat lives only in the 'days' schema field), nor anything about data freshness or scope limits of CTA's records.

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 dense sentence that front-loads the scope ('For a given congressional committee') before enumerating return values. Nothing is redundant, though the sentence is long enough that the enumerated outputs could be easier to scan as a short list.

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 naming the returned fields (members, trade counts, percentage of committee). For a two-parameter read tool this is nearly sufficient; the main omission is any note on data completeness or how partial committee-name matches resolve.

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 both parameters are already documented, including the 45-day disclosure lag and default of 90 days. The description only restates 'last N days' and 'given congressional committee' without adding format, matching behavior, or partial-match semantics beyond what the schema provides. 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 uses a specific verb and resource ('returns which members have stock trades... for a given congressional committee') and spells out the three outputs: member list, trade counts, and committee participation percentage. It does not name any sibling to distinguish itself from, but the committee-level aggregation scope makes it separable from get_member_trades and get_trade_feed on inspection.

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 implied by 'for a given congressional committee', which signals the committee-aggregate use case, but there is no explicit when-to-use or when-to-prefer-a-sibling statement (e.g. versus get_member_trades for an individual, or get_aggregate_stats for cross-committee figures). The agent must infer placement from the sibling list.

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