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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description usefully adds what the payload contains (buy/sell counts, total volumes), but says nothing about the aggregation window, pagination over 6 optional params, or whether results are grouped by ticker.

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 sentences, front-loaded with the purpose, no filler. Efficient but leaves no room for the guidance an agent needs.

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?

With all six params fully documented in the schema and annotations carrying the safety profile, the essentials are covered. The remaining gaps — the 'by ticker' ambiguity and no routing to get_insider_trades — are the ones that actually affect correct invocation.

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 coverage is 100%, so the baseline would be 3, but the description says results are 'by ticker' while the schema exposes no ticker parameter — an agent could reasonably look for one that doesn't exist. It adds no clarifying meaning to the four date-boundary filters or the pagination pair.

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?

States a specific verb and resource — aggregated insider trading sentiment per stock, with buy/sell counts and volumes. It implicitly distinguishes itself from the raw-trade sibling but never names it, so the differentiation is left to inference.

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 contains no when-to-use statement and no mention of the obvious alternative, get_insider_trades. An agent must guess whether it wants raw trades or this aggregated view.

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