tenero_market_summary

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

With no annotations, the description carries the full burden and does disclose some useful traits: no authentication required, Tenero API as source, and weighted pricing across all pools. It does not mention rate limits, caching, real-time freshness, or explicitly state read-only behavior beyond the word 'Get'.

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 mostly efficient, stating the core purpose before secondary details. The trailing tip about earning_opportunities is extraneous for selecting or invoking this tool, so it is not maximally 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 two-parameter read-only query with no output schema, the description adequately explains the return composition and authentication requirement. It remains incomplete around sibling differentiation and operational behavior such as freshness or limits, leaving the agent with minimum viable context.

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 description coverage is 100%, so both chain and contractId are fully documented in the schema. The description only implies a token parameter via 'this token' and adds no chain or contractId guidance beyond the schema, making the baseline 3 appropriate.

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 a token market summary, including price history, 24h volume, pool liquidity, and weighted price across pools. This clearly communicates what the tool does. It does not, however, distinguish itself from close siblings such as tenero_market_stats or tenero_token_info.

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 when-to-use guidance or comparison with alternative market-data tools. The only cross-reference points to earning_opportunities, which is unrelated to choosing between this and sibling Tenero market tools.

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