get_compound_market_info

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

Annotations already indicate readOnlyHint=true and idempotentHint=true. The description adds value by detailing exact return fields: base-token metadata, totalSupply/totalBorrow, utilization, APRs, pause flags, and full collateral list. It also confirms no wallet is needed, enhancing transparency beyond annotations.

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 two sentences with no wasted words. The first sentence states purpose and key constraint (no wallet required). The second details return fields and use cases. It is front-loaded and efficient.

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?

Despite no output schema, the description comprehensively lists all returned data: base-token metadata, supply/borrow stats, APRs, pause flags, and detailed collateral-asset list with 9 attributes per asset. It also covers use cases, making the tool fully understandable.

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?

Input schema has 100% coverage with descriptions for both parameters (chain with enum, market with pattern). The description adds a concrete example ('cUSDCv3 at 0x...') and explains market state use, which enhances understanding beyond the schema alone.

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 'Fetch structured market info for a single Compound V3 (Comet) market — no wallet required.' It specifies the verb 'Fetch', the resource 'market info', and distinguishes from sibling tools like get_compound_positions by emphasizing it returns market data, not user positions. The use cases further clarify its scope.

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 this to explain market state, answer "what are the listed collaterals for cUSDCv3", or diagnose an incident.' It provides clear when-to-use guidance and notes 'no wallet required,' implying it does not need authentication. It lacks explicit when-not-to-use statements, but the context is sufficient.

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