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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is covered. The description adds real value with the sha256-verified bundle integrity guarantee and the required scope, but says nothing about pagination semantics despite two paging-related parameters.

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 tight sentences, front-loading the verb+resource and the integrity guarantee, then the access prerequisite. Nothing is wasted.

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 paginated export tool with no output schema and no annotations on paging, the description leaves include_messages and the cursor workflow entirely to the schema. Adequate but with clear gaps an agent would need to fill from other sources.

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%: after_key and max_bytes are documented in the schema, but include_messages has no description in either the schema or the description, which is a meaningful gap for a parameter that changes the bundle contents. The description adds no parameter information beyond the schema.

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 states a specific verb (Export) and resource (a workspace) and adds the distinguishing detail 'portable, sha256-verified bundle', which separates it from read-only siblings like list_workspaces or retrieve_memory. It does not explicitly name restore_context as the counterpart, so sibling differentiation is implied rather than stated.

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 only usage guidance is the prerequisite scope 'context:export'. There is no statement of when to export, when the paginated cursor should be used, or how it relates to restore_context, which the schema's page cursor clearly presupposes.

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