blockrun_surf

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

No annotations provided, so the description carries the burden. It discloses pricing settled in USDC, method routing, pre-validation to avoid charges on missing params, and agent_id for budget tracking. No destructive behavior is indicated, and the description is transparent about costs and error handling.

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 moderately lengthy but well-structured with bullet points, examples, and a link to the full catalog. It front-loads the purpose and includes necessary details without excessive redundancy. Could be slightly more concise, but the structure aids readability.

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, and the description does not explain the return format or structure of responses. Given the tool's complexity (84 endpoints), missing output details may leave the agent uncertain about how to parse results. The description adequately covers input and pricing but lacks output completeness.

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 baseline 3. The description adds value by providing concrete examples for each common path, explaining the auto-routing between params (GET) and body (POST), and noting that agent_id is for budget tracking. This goes beyond mere schema listing.

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 is a unified crypto data API via Surf, listing 84 endpoints across multiple categories (CEX, on-chain, prediction markets, etc.). It distinguishes from sibling tools by being the general data API, while other blockrun tools are specialized (e.g., blockrun_price for specific price queries).

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 provides pricing tiers, common endpoint paths, method routing (GET vs POST), and error handling (400 if missing params). It suggests browsing the full catalog. However, it does not explicitly contrast when to use this tool versus siblings like blockrun_price or blockrun_search for similar queries.

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