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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered structurally. The description adds that it returns a live snapshot for one or more symbols, but says nothing about latency, rate limits, staleness, or behavior when a symbol is unknown. 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?

Two sentences, both front-loaded and information-dense: the first gives scope, the second enumerates the returned fields. Nothing is padded or redundant.

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 rich annotations and an output schema present, the description needs only scope and payload summary, which it provides. It is essentially complete for a simple read tool, missing only sibling differentiation and any rate/limit caveat.

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% and the single 'symbols' parameter is fully documented in the schema with an example and min/maxItems. The description's phrase 'one or more crypto futures symbols' only restates the array nature, adding no format, naming-convention, or batching guidance beyond the schema. Baseline 3 applies.

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 and resource: 'Get real-time price data for one or more crypto futures symbols', plus the payload contents. This is clearly distinguishable from a generic fetch, but it never names or contrasts with siblings like get_candles (historical) or get_market_stats (aggregate), so an agent must infer the boundary from the word 'real-time' alone.

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?

Usage is only implied: 'real-time price data' suggests a live snapshot rather than historical series, which is a weak signal against get_candles. There is no explicit when-to-use, when-not-to-use, or named alternative, and no note on batching limits or appropriate call frequency.

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