get_crypto_market

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

Annotations already declare readOnly/idempotent/non-destructive, so the safety profile is covered. The description adds genuinely non-redundant behavior: it is public and keyless, always returns a fixed snapshot set, and clarifies that each include returns limit rows (1-500).

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?

Front-loaded with scope and auth first, then the return contract, then the optional expansions. Every clause carries information; minor density in the include/interval/limit sentence, but nothing wasted.

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 needn't be fully spelled out, yet the description still names the snapshot contents. Combined with the include semantics and limit range, an agent has enough to call it correctly; only the default limit and interaction with the base snapshot are unstated.

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 description coverage is 0%, so the description must carry parameter meaning, and it does: it names the three valid include values, ties interval to candles, and constrains limit to 1-500 rows per include. The symbol format is given by example. It omits the limit default (30) and whether limit applies to the snapshot too, so not a full 5.

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: public Binance USD-M futures market data for one symbol, naming the exact snapshot fields returned. It does not explicitly differentiate from the overlapping sibling get_candles, which it partially duplicates via the 'candles' include option.

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 API key' establishes a key prerequisite for public data access, and 'Always returns the snapshot' tells the agent what happens by default. However, it never says when to prefer this tool over get_candles or get_quote, leaving the choice between overlapping siblings to inference.

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