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

Beyond the annotations, it discloses the one-time private workflow_manage_token and that retries neither rotate nor reissue it, the exclusion of the close summary receipt from the step count, the non-canonical status of the session_workflow_id/workflow_id metadata, and the trust boundary ('Records Zambo's claims, not issuer authentication'). The idempotent/non-destructive/read-only claims in the annotations are actively reinforced by the immutable-snapshot and repeat-call semantics, adding real context rather than repeating structured fields.

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?

Five tightly packed sentences, front-loaded with the core action before the idempotency, token, and trust details. Everything earns its place, though the receipt-byte jargon makes it denser than ideal for a quick scan.

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 an output schema present, 100% schema coverage, and full annotations, the description only needed to cover behavioral quirks — and it does: idempotency semantics, token lifecycle, step-count exclusion, metadata treatment, and honest trust claims. Nothing an agent needs to call it correctly is missing.

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 100%, so the schema already documents all five inputs including aliases and the _zambo_key secrecy note. The description adds little about the input parameters themselves (it discusses identifiers that are largely outputs), so the baseline of 3 applies.

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: 'Create or return an immutable snapshot of this job's eligible receipts.' It also distinguishes the snapshot workflow_id from the live-ledger session_workflow_id, giving the agent a clear mental model of what it produces. It never names or contrasts with the obvious sibling workflow_seal, so it falls short of full sibling differentiation.

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?

Usage is implied rather than stated: the agent learns that repeating the call with unchanged receipts yields the same snapshot, and that later calls create a new snapshot. There is no explicit when-to-use guidance and no routing to or away from alternatives such as workflow_seal or the continuity tools.

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