get_market_snapshots

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

Annotations already declare readOnlyHint=true, so the description does not need to reiterate read-only nature. The description adds some context about data types but does not disclose other behavioral traits like pagination, rate limits, or array return format. No contradictions with 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 a single, clear sentence. It is slightly wordy (e.g., 'history' could be omitted), but overall concise and well-structured with no redundant information.

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?

The description is adequate given the annotations and schema coverage. It explains what the tool returns without needing an output schema. However, it could mention that the response is an array of daily snapshots or that the 'days' parameter controls the history length, though the schema already specifies that.

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% (all 4 parameters have descriptions). The description adds general context but no additional meaning beyond what the schema provides, so baseline score 3 is 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 clearly specifies the tool provides daily snapshots for a specific market, listing multiple data points (price, TVL, volume, revenue, rates, user counts). The verb 'get' and resource 'market snapshots' are distinct from sibling tools like 'get_market' (single snapshot) and 'get_markets' (list).

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?

No explicit guidance on when to use this tool versus alternatives. While the description implies historical data, it does not contrast with sibling tools like 'get_market' for current state or 'compare_protocols' for cross-analysis. Agents would benefit from usage hints.

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