get_market_chart

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

No annotations are provided, so the description carries the full behavioral burden. It says nothing about granularity/interval, response shape, whether 'days' caps are enforced, or rate limits, and omits the fact that the sibling get_historical_price_data may return the same underlying series.

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?

A single short, front-loaded sentence with no filler or repetition. It is efficient, though its brevity borders on under-specification rather than true conciseness.

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 tool with no annotations and no output schema, the description is too thin: it neither routes the agent away from overlapping price siblings nor explains the semantics of the required 'symbol' argument or what the chart data contains.

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 only 50%: the 'days' parameter is documented in the schema, but 'symbol' has no description at all. The description says 'for a token' but never clarifies that 'symbol' is the token identifier or what format it takes, so it does not compensate for the coverage gap.

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?

States a clear verb ('Get') and resource ('historical price chart data for a token'), so an agent knows the general operation. However, it fails to distinguish itself from the near-identical sibling get_historical_price_data (and get_fan_token_price, get_multiple_prices), leaving ambiguity about which price tool to pick.

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 when-to-use guidance, no prerequisites, and no alternatives named despite several overlapping price siblings. The agent must infer entirely from the name that this is the charting variant rather than the raw historical data variant.

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