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

With no annotations, the description carries the full behavioral disclosure burden. It does disclose an important behavioral constraint: avg_lag_excess is only shown when a member has at least 5 priced purchases, and it instructs never to quote it without the S&P 500 move. However, it does not state whether this is a read-only operation, mention rate limits, or clarify how the data is returned beyond high-level content.

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?

The description is relatively compact and front-loaded with the core purpose, then adds a conditional-data caveat and a source reference. The parenthetical lists are dense but useful. The 'Same data as coldpine.io/...' sentence adds a reference point but is not necessary for tool invocation, keeping it from being a perfect 5.

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 there is no output schema and no annotations, the description does a solid job of outlining what the agent will get: a site-wide summary, a per-member board, and the conditional avg_lag_excess metric. The main gap is that it does not explain how `sort` and `limit` shape the results, but for a 2-parameter tool the overall picture is reasonably complete.

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 input schema has 0% description coverage, so the description must compensate by explaining the parameters. It does not mention `sort` or `limit` at all. The description's mention of metrics like 'trades past 45 and 90 days' and 'median lag' implicitly maps to some enum values, but that connection is left for the agent to infer rather than explicitly explained.

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's purpose: it reports how quickly Congress discloses trades relative to the STOCK Act's 45-day window, covering both site-wide summaries and per-member boards. It mentions specific metrics and the conditional avg_lag_excess field, making the purpose clear. However, it does not explicitly differentiate itself from sibling tools such as congress_leaderboard or members_vs_market.

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?

There is no guidance on when to choose this tool over its siblings, no exclusions, and no comparison to alternatives. The description only provides details about what the tool returns and references an external data source, but never tells the agent 'use this when...' or 'use that instead when...'.

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