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

No annotations are provided, so the description carries the full disclosure burden. It does disclose the scope and granularity of what is computed (including the "since records began + 30/60/90d" windows), but says nothing about cost, freshness of data, or result size — low risk given zero parameters, yet not fully transparent.

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 front-loaded sentence that packs the full metric list with no filler. It is dense but readable; the parenthetical shorthand ("since records began + 30/60/90d") and the unexplained acronym "CTA" cost it a bit of clarity.

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 zero-parameter, read-only aggregate with no output schema, the description supplies the one thing an agent needs: what the response contains. Only the absence of any note on data currency or expected response shape keeps it from being fully 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 tool takes no parameters, so there is nothing for the description to disambiguate. The baseline of 4 applies; the description cannot be faulted for missing parameter meaning when the schema is empty.

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?

Uses a specific verb ("Get") with a concrete resource ("high-level stats on records") and enumerates the metrics returned: trade counts across time windows, member coverage, average filing delay, and sector breakdown. That enumeration differentiates it from single-dimension siblings such as get_chamber_breakdown, get_party_breakdown, and get_top_tickers, though it never names those siblings directly.

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?

"High-level stats" implies a summary/overview use case, but there is no explicit statement of when to choose this over the breakdown tools or what question it answers. An agent must infer that this is the entry-point overview tool before drilling into the more specific siblings.

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