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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description usefully adds the window default (ALL) but says nothing about response shape, timezone/timestamp semantics, or what 'latest' frame means beyond the schema.

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?

Two short sentences plus a one-line example, front-loaded with the core action and the window default. Slightly telegraphic ('price history + latest') but no wasted prose.

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?

An output schema exists, so return values need not be described. However, with a required address parameter and an undocumented chainId at 0% schema coverage, the definition leaves real gaps an agent must guess at before invoking.

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 0%, so the description carries the burden. It clarifies the window parameter's default and accepted values, but leaves address (the required param) and chainId entirely unexplained — no format hints (contract address vs. market id) or how chainId is resolved.

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 specific verb (get) and resource (price history + latest frame for a market), which is clear enough to distinguish it from siblings like problee_get_market_trades or problee_get_market_depth. It stops short of explicitly naming what those siblings cover, so the differentiation must be inferred.

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 example ('Read the 1D price history for a market') and the window options imply how to use it, and the default (ALL) is stated. There is no explicit when-to-use vs. when-to-use-an-alternative guidance, e.g. charting vs. trade-by-trade retrieval.

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