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

Annotations already declare idempotentHint=true and destructiveHint=false, yet the description adds substantial context beyond them: the one-time private workflow_manage_token that is not rotated or reissued on retries, the exclusion of the close summary receipt from its own step count, and the caveat that it records Zambo's claims rather than issuer authentication. These are meaningful operational and trust caveats an agent could not infer from the 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?

The core purpose is front-loaded in the first sentence and the paragraph stays on-topic with no filler. However, the sentences are long and densely packed with internal jargon (workflow_id vs. session_workflow_id, canonical receipt bytes), which makes it harder to scan than it needs to be.

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?

An output schema exists, so return values need not be explained, and the description still covers idempotency, snapshot identity, token issuance, and the required argument. For a stateful close operation, the remaining gap is minor, though it never explains what happens to the live ledger after close or how snapshot contents can be retrieved later.

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 the schema already documents all seven parameters in detail. The description adds only the required-argument callout for _session_id, which is mildly useful because the schema's own description labels it 'Optional' while the required list includes it. Otherwise it contributes no syntax or constraint information beyond the schema, so baseline 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?

The description names a specific verb+resource: create/return a fixed snapshot containing a verifiable receipt of every persisted receipt in the job. It distinguishes the ephemeral snapshot workflow_id from the live session_workflow_id ledger, which helps an agent understand what it is producing. It does not differentiate from the sibling workflow_seal, so it stops short of a 5.

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?

It explicitly covers repeat-call behavior: unchanged receipt data returns the same snapshot id, while new receipts produce a separate snapshot. That is actionable guidance about retries vs. follow-up calls. It gives no guidance on when to prefer this over workflow_seal or when not to close, so 4 rather than 5.

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