Get Settlement Print

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

Annotations already indicate readOnly, idempotent, non-destructive behavior. The description adds genuinely non-obvious details: the result is signed, deltaMs is not part of the signed content, sampling/retention are bounded, and metadata is not signed. 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?

Compact and front-loaded: the first sentence states the purpose, and each following sentence adds essential operational detail—time formats, deltaMs, sampling limitations, and verify_print preservation. No filler or 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?

Even without an output schema, the description covers the relevant response semantics: deltaMs, priceText, kid, and signed vs. non-signed metadata. This is enough for an agent to invoke the tool and correctly feed output into verify_print.

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 describes symbol but not at. The description compensates by explaining the accepted formats for at (ISO-8601 or epoch milliseconds) and the meaning of deltaMs. It adds meaningful semantics beyond the schema, though it does not elaborate on symbol beyond what the schema already provides.

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 plus resource: 'get the recorded signed index print nearest a requested time' from '/api/index/v1/print'. This clearly distinguishes it from live-read siblings while specifying the exact operation.

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?

Provides important usage context: a recorded print may differ from a live read, deltaMs measures distance from the requested time, and priceText/kid should be preserved for verify_print. It does not explicitly name alternatives like get_index_price, but effectively implies when a signed historical print is needed.

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