agentFriendly_asset_mcap_history_slug

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

No annotations are provided, so the description must disclose behavioral traits. It only states 'optimized for AI analysis,' which is vague and non-behavioral. No mention of idempotency, permissions, rate limits, or side effects. For a read-only query tool, this is insufficient.

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 short but includes a somewhat vague term ('optimized for AI analysis') that could be omitted or replaced with concrete details. It is not overly verbose, but lacks precision.

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?

With no output schema, the description should explain the return format. It does not. The tool is for historical data, but the description gives no indication of the response structure (e.g., time series of market cap values). Behavioral traits are also missing.

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 the schema already describes the parameters. The description adds no parameter-specific semantics beyond 'optimized for AI analysis,' which is not tied to any parameter. At baseline 3, the description does not add meaningful value over 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 it retrieves asset market cap history, with a specific mention of the data source (direct from mcap_history table) and optimization for AI analysis. This distinguishes it from sibling tools like assets_slug_marketcap-history, though not explicitly.

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 guidance on when to use this tool versus alternatives. Sibling tools include multiple history and market cap options, but the description does not provide any when-to-use or when-not-to-use information.

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