get_full_orderbook

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

No annotations provided, so description carries full burden. Discloses requirement for ALPHA_API_KEY, clarifies input format (UUID vs marketAppId), and mentions return shape (same as websocket orderbook_changed.orderbook). Adds behavioral context beyond schema, though could additionally state that it is a read-only operation.

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?

Four short, clear sentences front-loaded with purpose, followed by key constraints (API key, input type, output shape). No redundant or irrelevant information; every sentence earns its place.

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?

Tool is simple with 1 parameter and no output schema. Description adequately covers purpose, auth, input clarification, and return shape. Missing details on error handling or rate limits, but for a low-complexity tool, this is reasonably complete.

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?

Only one parameter, marketId, with full schema coverage (100% described). Description adds crucial clarification that input is the Alpha market ID (UUID) and not marketAppId, which adds meaning beyond the schema description. Baseline 3 upgraded due to extra value.

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?

Describes fetching a full processed orderbook snapshot from the Alpha REST API for a market. Clearly distinguishes input (Alpha market ID UUID) from marketAppId, which differentiates it from sibling tools that might use the latter. Verb 'Fetch' combined with resource 'full processed orderbook snapshot' is specific.

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?

Implies usage for fetching a static snapshot, but does not explicitly state when to use this tool versus alternatives like get_orderbook or stream_orderbook. No direct exclusions or comparison to siblings.

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