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

Annotations already declare readOnly, idempotent, non-destructive behavior. The description adds useful context: the workspace is private, membership is required, and reading is intended to resume another agent's state. This exceeds the structured annotations without contradicting them.

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?

Three short sentences, with the action and access constraint front-loaded, the intended usage pattern second, and sibling listing last. Every sentence contributes information with no filler.

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?

Combined with a full input schema, an output schema, and strong annotations, the description covers the tool's role, access restriction, and orchestration pattern. It slightly under-specifies what 'state' means, but the output schema and note_key parameter cover the target.

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 parameters including payment_signature. The description adds no further parameter-level meaning, but it is not required to at this coverage level.

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 first sentence names a specific verb and resource ('Read state from a private workspace') and adds a membership restriction. It also names the sibling tools, making the distinction between read/write/list explicit enough for an agent to select the correct operation.

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 gives an explicit invocation context: use after vc_workspace_write to resume where another agent left off. It lists sibling tools but does not fully state when to choose read over workspace_list or workspace_write beyond the 'member only' and sequencing hints.

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