tenero_token_info

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

With no annotations, the description carries the full behavioral burden and does disclose useful context: it is powered by api.tenero.io and requires no authentication. However, it omits rate limits, data freshness, error behavior, and whether the read operation is idempotent/cacheable.

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 front-loaded and appropriately short, with the core purpose stated first. The final tip about `earning_opportunities` is tangential to invoking this tool, so the structure is good but not perfectly economical.

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 two-parameter read tool with fully documented schema fields and no output schema, the description is largely complete. It lists the key return fields and notes the unauthenticated API source, though it could better distinguish this tool from the sibling `get_token_info`.

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 both `chain` and `contractId` are already well-documented in the schema. The description adds no parameter-specific meaning beyond the schema, which is acceptable at baseline 3 given the high coverage.

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 states a specific verb and resource: "Get token details" and lists metadata, current price, market cap, and 24h volume. It is clear what the tool returns, but it does not differentiate itself from the sibling `get_token_info` or explain what makes this Tenero-backed variant distinct.

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?

There is no explicit guidance on when to use this tool versus alternatives such as `get_token_info`, nor any prerequisites or exclusions. The trailing tip to call `earning_opportunities` is a cross-sell rather than usage guidance for this tool.

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