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

Annotations already carry readOnly/idempotent/non-destructive/openWorld, so 'this read does not trade' is largely redundant. The description does add genuinely new behavioral context: the payload is a composite (live 24/7 metrics, cross-DEX sibling spreads, your open Gambits on those symbols, OCPI/OTPI snapshot) and Tesseract clearing is conditionally omitted unless TESSERACT_REFERENCE_FEED_ENABLED is on — a real data-availability caveat not expressible in 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?

Front-loaded with purpose and invocation mode before the long return-value enumeration, and the enumeration is justified because there is no output schema. It is dense to the point of being a run-on, and 'This read does not trade' repeats what readOnlyHint already says.

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 fully covers what comes back (quote/perp fields, cross-DEX spreads, open Gambits, OCPI/OTPI) and flags the feature-flagged omission, so an agent knows both how to call it and what to expect. The only residual gap is the preset-vs-symbols routing ambiguity noted above.

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 baseline is 3, and the description does enrich mandate_id (reads YOUR saved Gambit's name, interval, whitelist). However it muddies the schema by writing 'preset=ai_memory_compute (or a comma-separated symbols list such as xyz:SKHX,...)', which implies the symbol list is passed through preset when the schema has a distinct symbols parameter (maxLength 512) — an ambiguity an agent must resolve from 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?

States a concrete resource (a 'shareable radar' over a mandate or symbol list) plus the (api:read) scope, which is specific enough to distinguish it from plain quote tools like get_live_snapshot or get_prices. It does not explicitly name a sibling it is not, so differentiation is inferred from the dual-mode framing rather than stated.

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?

Gives clear routing: use mandate_id to read your saved Gambit, or preset=ai_memory_compute for the memory/optical/AI-compute watch. It states the positive conditions for each mode but never says when to prefer this over get_mandate, get_live_snapshot, or get_sector-style siblings, nor any exclusions.

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