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

With no annotations provided, the description carries the full burden of behavioral disclosure. It does not state whether the operation is read-only, any side effects, data freshness, pagination, or the shape of the returned data. The mention of 'same data' is a source reference, not a behavioral trait.

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?

Two concise sentences that front-load the core function (ranking members) and list the key options without redundancy. Every clause adds value, and the external reference is a single short clause.

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?

Given no output schema, the description should explain what the response contains (e.g., member names, stats, ordering) and how limit/filters affect results. It does not mention return format or the behavior of the limit parameter, though the defaults and enums in the schema help. It is adequate for a simple list but lacks detail on output and usage context relative to siblings.

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?

The description adds meaning to the sort parameter by explaining each enum value (trade count, volume as sum of amount-range midpoints, average size, speed). It also confirms chamber and party are filters, though the schema already documents chamber's enum. With only 25% schema coverage, the description compensates well for the sort values.

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 clearly states the tool returns a ranking of members of Congress by disclosed trading activity, with explicit sort options (trade count, volume, average size, speed) and optional chamber/party filters. It distinguishes itself from siblings that focus on individual filings or members, though it does not name them 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?

The description implies this is for leaderboard/overview data (e.g., 'ranked by'), but it does not explicitly state when to use it versus alternatives like members_vs_market or search_members, nor does it provide exclusions. The 'Same data as coldpine.io/leaderboard' is external and not a sibling comparison.

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