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

Annotations already declare this is a non-read-only, non-destructive, non-idempotent write. The description adds meaningful context beyond that: the operation signs content and is chained to the previous checkpoint, implying append-only lineage and an auth scope requirement. It omits what the caller gets back and whether repeat calls append new checkpoints, so the added value is real but partial.

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?

Two compact sentences with the core action first and the prerequisite second. No filler, no restatement of the title.

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?

No output schema exists, so the description should carry more of the burden; it explains the action, chaining, and auth scope but leaves out the return value and the interaction with idempotency_key. Adequate to invoke, not fully sufficient to predict behavior.

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 50%: idempotency_key is documented in the schema, but workspace_id is undocumented there and the description does not compensate — it never says what workspace_id identifies or that it must be the target workspace. The description mentions no parameters at all.

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 ('Sign a hash manifest'), the exact resources covered (memories and tasks), and the chaining relationship to prior checkpoints. This clearly separates it from get_checkpoint, list_checkpoints, and export_context, though it never names those siblings explicitly.

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 'Requires scope context:export' line gives a concrete prerequisite, which is genuine usage guidance. However, there is no statement of when an agent should create a checkpoint versus list/get one, nor any exclusion conditions.

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