get_hip4_l4_diffs

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

Annotations already declare readOnlyHint and idempotentHint, so the description is not required to repeat safety traits. It adds value by noting the 'Pro+ tier' access restriction and specifying that it returns 'new orders, modifications, cancellations, fills', which discloses the nature of the data. No contradictions 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?

The description is brief yet complete, consisting of three focused sentences. The first sentence states the primary action, the second clarifies the input format, and the third describes the output. Every sentence contributes to understanding without redundancy.

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?

Given the existence of an output schema and detailed parameter descriptions, the description covers the essential functional aspects. It could be improved by adding guidance on when to use diffs versus full orderbook or history tools, but it is largely adequate for a read-only tool with rich annotations and schema.

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 includes descriptions for all parameters. The description adds extra context for the coin parameter (canonical vs legacy forms) and cross-references get_hip4_instruments for listing coins, which enhances understanding beyond the schema. Other parameters are adequately covered by 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?

The description clearly states the tool retrieves HIP-4 L4 orderbook diffs for a specific coin, using a specific verb-noun structure. It distinguishes from siblings by specifying 'diffs' as opposed to full snapshots or history, and provides a concrete example (e.g., '0').

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 description implies usage for tracking order-level changes via 'raw order-level changes' and 'over a time range', but does not explicitly state when to prefer this over alternatives like get_hip4_l4_orderbook or get_hip4_order_flow. No exclusions or direct comparisons are provided.

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