scan_bottoms

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

Discloses payment model, cost, trial, retry header, and no-account requirement. No annotations exist, so description carries burden. Does not mention destructive effects (presumably read-only).

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 purpose, structured with key details. Slightly verbose on payment, but acceptable for clarity.

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?

No output schema, but description explains returns are ranked list. Covers cold start and payment. Adequate for the tool's complexity.

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%, and description adds context: limit default/max, symbols optional with default set. Adds value beyond 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 it scans the market for coins at a bottom, ranked most-bottom first. It distinguishes from siblings like scan_tops by specific mention of 'bottom' vs 'tops'.

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?

Provides guidance on payment, cold start (no symbol needed), and mentions the free pitch tool. Lacks explicit when-not-to-use but context differentiates from siblings adequately.

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