bundle_scope

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

No annotations are provided, so the description bears full responsibility. It explains the tool scans the first 3 blocks and returns risk score, bundle wallets, and dump status. However, it does not disclose potential costs, API key requirements, or error handling for invalid addresses, leaving some behavioral gaps.

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 three concise sentences: first states purpose, second details scanning logic and outputs, third gives usage advice. No redundant information, and each sentence adds value.

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 the tool's simplicity (one parameter, no nested objects, output schema present), the description adequately covers what the tool does and when to use it. It does not detail the output schema (which is separate) but is otherwise complete for a data-checking tool.

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 input schema has one parameter ('address') with 0% description coverage. The description only implies it is a token address on Base but does not specify format, required network, or any constraints. Since schema coverage is low, the description should compensate but falls short.

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 detects token launch bundles and snipers on Base, scanning the first 3 blocks for coordinated buys. It specifies the resource (token launches), verb (scans), and outputs (risk score, bundle wallets, dump status). This clearly distinguishes it from sibling tools like token_launches or contract_check.

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 explicitly says 'Use before buying any new token to check if the launch was bundled,' providing clear when-to-use guidance. It does not mention when not to use or alternatives, but the context is sufficient for typical use.

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