explorer_get_historical_price

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

Annotations already provide readOnlyHint and openWorldHint. The description adds the 'daily' granularity, which is useful behavior context. However, it does not disclose response format, potential limitations, or other behaviors. No contradiction 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, concise, front-loaded sentence. It wastes no words and immediately communicates the tool's action and purpose.

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 tool has no output schema, so the description must compensate. It states the core function but does not specify the return format (e.g., array of daily prices) or any constraints. The sort parameter in the schema implies a list result, making the description minimally sufficient, but more detail would improve completeness.

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 descriptions cover 100% of parameters with clear formats. The description adds context by noting 'daily' and 'native token', which clarifies that startDate/endDate should be used for daily price queries and that chainId refers to a chain's native token. This adds value beyond the schema.

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 action ('get'), resource ('historical daily native token prices'), and scope ('date range'). It distinguishes itself from siblings like explorer_get_native_price (current price) and market_get_token_history (any token) by specifying 'native' and 'daily'.

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 implies usage by stating the tool's function, but it does not explicitly mention when to use it over alternatives like market_get_token_history or explorer_get_native_price. There is no guidance on exclusions or alternative tools, which is a gap given many similar siblings.

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