token_info

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

No annotations exist, so description alone must clarify behavior. It mentions data source ('from the explorer') and network restriction, but doesn't disclose potential latency, rate limits, or error handling if token is invalid. Minimal but adequate for a read-only info tool.

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?

A single sentence with the core purpose and a constraint. No wasted words, front-loaded with actionable info. Very concise.

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?

For a simple lookup tool with one parameter and no output schema, the description covers the essentials: what data is returned and the network restriction. Missing error scenarios or data freshness, but these are minor for this complexity level.

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 already describes the sole parameter 'token' as 'Symbol or contract address' (100% coverage). The tool description adds no further detail about parameter format, valid values, or behavior, so it meets the baseline but adds no extra value.

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 provides 'Detailed token info from the explorer: supply, holders, market data.' This specifies both the resource (token info) and scope (supply, holders, market data). Among sibling tools like get_token_balance or token_metadata, this distinguishes itself as a comprehensive info gatherer.

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 constraint 'Mainnet only' gives clear context on when to use, but no explicit guidance on when not to use or alternatives. However, the description implies appropriate use for general token queries, differentiating from single-aspect tools.

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