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

Annotations already declare readOnly, non-destructive, closed-world, and the description adds real behavioral context beyond them: the state is 'Non-atomic observed state' and the call 'never executes work or renews leases.' Those two facts prevent an agent from mistaking this for a lease-refresh or action-triggering call, which is genuinely valuable given the 'resume' framing.

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: the first front-loads the payload contents, the second delivers the behavioral caveats and the continuation rule. No filler, and the most decision-relevant caveat (non-atomic, no side effects) is placed where it is easily scanned.

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 shape need not be documented, and the annotations cover the safety profile. The description still adds the pagination continuation rule and the non-atomic/no-side-effect guarantee, which are the non-obvious facts needed to call it correctly; only the input parameter semantics remain thin.

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 0%, so the description must carry parameter meaning, but it mostly lists what is returned rather than explaining inputs. It obliquely references the 'checkpoint' and 'explicit entry references' parameters and the memory_reference states, but leaves limit, max_tokens, task_id, and space_id entirely unexplained even though max_tokens governs a BUDGET_TOO_SMALL retry path.

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 uses a specific verb ('Read') plus a concrete enumeration of the resource state it returns (checkpoint, memory_references with four lifecycle states, task, space, assigned tasks, leases, entry references). An agent can tell this is a composite resume-context reader rather than a simple entity getter. It stops short of naming which sibling to use instead when a narrower read is wanted.

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 description implies usage through 'Follow returned component cursors with their original methods,' which tells the caller how to continue after reading. However it never states when this composite read is preferable over narrower siblings like get_space, get_memory, or get_operation, so the selection guidance is inferred rather than explicit.

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