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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, covering safety. The description adds contextual detail about the type of anomalies but does not disclose return format, pagination, or any other behavioral nuance. It neither contradicts annotations nor enriches them significantly.

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 a single, compact sentence that front-loads the core function ('Odd things from the last hour on Pons launches') and then lists illustrative examples. There is no redundant or verbose language.

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 no output schema and no parameters, the description should convey what the tool returns. It lists anomaly categories but does not specify the output structure (e.g., list, count, details). This leaves some ambiguity for an agent expecting to consume the results, though the read-only nature and zero inputs reduce the risk of misuse.

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 has zero parameters, so schema coverage is trivially 100%. Per calibration, a baseline of 4 applies since there are no parameters to describe; the description does not need to elaborate on inputs.

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 surfaces 'odd things from the last hour on Pons launches' with specific examples (insider selling, liquidity leaving, serial launcher, large burn). It conveys a distinct purpose of anomaly detection, though it does not explicitly differentiate from siblings like smart_money or moving_now, which could overlap in intent.

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 provides temporal context ('last hour') but offers no guidance on when to use this tool versus alternatives. There is no mention of when not to use it or which sibling tools would be more appropriate for related queries, leaving the agent to infer its place.

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