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

Beyond the readOnlyHint annotation, the description discloses meaningful behavior: data is sourced from available published filings, results include coverage metadata and unknown-value counts, scope is through today in the current UTC month, and result counts are capped by key type. These details materially set expectations without contradicting the annotation.

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?

Three sentences, each earning its place: the core aggregation scope, the data caveats, and the entitlement caps. No filler or redundant restatement of the schema.

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 read-only aggregator with only two parameters and no required output shape, this is complete: purpose, time window, data caveats, output metadata, and limits are all covered. An agent can select and call it correctly without missing critical context.

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 the schema already documents `kind` and `month` fully, including accepted values and the current-month-only restriction. The description adds no parameter-specific semantics beyond what the schema already states, so the 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-resource combination: 'Rank ticker activity aggregated from available published filings by transaction date' for the current UTC month. This clearly distinguishes it from trade-list siblings like list_insider_trades and list_congress_trades, which would provide individual filings rather than a monthly aggregate ranking.

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 gives clear context: use this for current-month aggregated ticker rankings from insider or congressional filings, and it warns 'this is not total market activity' and states key limits. It does not explicitly name alternative tools or state when not to use it, so it stops short of a 5.

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