recent_whales

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

No annotations are provided, so the description carries the burden. It discloses 10-min cache, meta fields (cacheAgeSeconds, chainCount, signalCount), and that it returns top-3 slice. Does not mention potential latency or data staleness beyond cache, but is fairly 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?

Front-loaded with key message, but the description is somewhat lengthy with multiple clauses. Every sentence adds value, but could be slightly more concise. Still clearly structured.

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?

Given no output schema and no parameters, the description adequately explains output fields (meta) and the 3-transfer limit. It provides context about chains and verifiable references. Enough for an agent to understand what to expect.

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?

No parameters, so baseline is 4. Description compensates by detailing output structure (meta fields) and behavior. It adds value beyond the empty schema.

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 'Get the latest 3 whale transfers right now' with specific verb and resource. It distinguishes from siblings by mentioning whale_activity (counts) and whale_movements (archived paginated data), ensuring no confusion.

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?

Explicitly tells when to use alternatives: 'use whale_activity for counts, whale_movements for paginated archive'. Also clarifies it's a live snapshot, guiding appropriate usage.

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