madeonsol_tokens_batch_buyer_quality

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

Provides valuable behavioral details beyond annotations: LRU cache with 5-min TTL, shared cache with single-mint endpoint, zero-cost for warm mints, and response includes cache_hits counter. No contradictions with annotations.

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?

Three concise sentences, each adding value: purpose, cache behavior, response detail. No redundancy or fluff.

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?

Covers key points: batch size, cache, response element. Lacks output format details but given no output schema and low complexity, is mostly complete.

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 already describes 'mints' parameter with constraints and description (1–50 base58). Description adds no new parameter info beyond cache context, so baseline 3.

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?

Clearly states it performs bulk buyer-quality scoring on up to 50 mints, distinguishing it from the single-mint sibling tool 'madeonsol_token_buyer_quality' via cache sharing note.

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?

Implies use when scoring multiple mints in one call, and mentions cache sharing with single endpoint. However, lacks explicit when-not-to-use or detailed alternatives.

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