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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description adds a genuine operational constraint beyond the annotations — 'Up to 25 tickers per call' — which tells the agent how to batch requests. It does not describe return shape or latency, hence not a 5.

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 core purpose and the constituent signals, closing with the hard cap. No filler or repetition.

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 rollup with annotations carrying the safety profile and a fully covered schema, the description supplies the essential content list and a batch limit. The lack of an output schema means the mental model of what comes back is only lightly sketched, leaving a small gap.

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% with a single well-documented 'tickers' parameter (comma-separated example given), so the schema carries param semantics. The description reinforces the batch limit but adds no syntax detail beyond what the schema provides; 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?

States a specific verb+resource ('consolidated activity rollup for a list of tickers') and enumerates the bundled signals (insider 30d net flow, Form 144 pressure, material events, cluster-sell flag), which implicitly differentiates it as a multi-signal rollup versus single-signal siblings like cluster_sells or company_insider_pulse. It stops short of naming any sibling explicitly, so it is clear but not fully self-locating.

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 batch/rollup framing implies usage (screening many tickers at once), but there is no explicit when-to-use, when-not-to-use, or routing to alternatives such as cluster_sells or company_insider_pulse. An agent must infer whether to call this versus the single-signal tools.

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