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

Annotations already declare destructiveHint=true and idempotentHint=false, so the safety profile is covered; the description adds real value beyond that by disclosing the authorization scope and the gating semantics of the signed checkpoint (signature, account ownership, content-hash match). It stops short of describing what an overwrite actually destroys or what state remains after a failed verification.

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 short sentences with zero padding: the core action comes first and the access requirement is appended as a compact constraint. Nothing here repeats the title or wastes words.

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?

For a destructive, non-idempotent, nested-object import with no output schema, the description covers the main flow and the auth prerequisite but omits the conflict-resolution semantics and any indication of what a successful or partially failed restore leaves behind. Adequate to attempt the call, not adequate to predict its effects.

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 60%, with bundle, checkpoint and idempotency_key documented in the schema itself; the description restates the checkpoint's role but adds no syntax or format detail. The notable gap is on_conflict, whose skip/overwrite behavior is explained in neither the schema nor the description.

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 pair (verify and import) plus the resource (an export bundle) and the target (a workspace), which is far more informative than the title 'Restore context'. The pairing with export_context is implied by 'export bundle' rather than named, so it is clear but not explicitly differentiated from siblings.

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?

Gives a hard prerequisite ('Requires scope context:restore') and frames the checkpoint as optional, which implies when to supply it. It never says when to prefer this over alternatives or when restore is inappropriate, and the choice between the on_conflict modes is left entirely unaddressed.

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