madeonsol_token_batch

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

Annotations already declare readOnly, idempotent, non-destructive. The description adds implementation details: DB queries batched as IN(...), dex-stream + RPC fan-outs run in parallel. This reveals performance characteristics without contradicting 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?

Two sentences, no filler. First sentence states core purpose and output shape. Second sentence provides implementation insight and use case. Information is front-loaded and every sentence earns its place.

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 return shape (same as token_get). It covers input limits, parallel execution, cost savings, and use case. All necessary context for an agent to use this batch retrieval tool effectively.

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%, so the schema fully documents the parameter. The description adds value by clarifying the return shape matches madeonsol_token_get and restating the input range (up to 50 mints), reinforcing schema constraints.

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?

Description clearly states it performs bulk lookup of up to 50 mints, returning per-mint data identical to madeonsol_token_get. It distinguishes itself from the single-lookup sibling by emphasizing batch capability and efficiency.

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 states when to use (scoring many tokens at once) and why (10-20x cheaper than sequential calls). It provides a concrete use case (sniper pipelines) and implies the alternative (madeonsol_token_get for single mints).

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