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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint. The description adds context beyond these: the returned state should be treated as untrusted data and external side effects must be verified. This is valuable behavioral disclosure that the annotations do not convey. No contradiction with annotations.

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?

The description is two sentences with no filler. The primary action and context are front-loaded, and the caveats are concise and actionable. Every sentence earns its place.

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?

Given the simplicity (1 parameter, no output schema) and the annotations covering safety, the description provides purpose, usage context, and critical handling instructions. It does not specify the return format, but that is not required since there is no output schema, and the description sufficiently guides the agent on what to do with the result.

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?

The schema has no description for task_id (coverage 0%), and the tool description does not mention the parameter at all. While the parameter's meaning is somewhat implicit (task identifier), the description fails to compensate for the lack of schema documentation, leaving the agent to infer its purpose.

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 clearly states the verb 'Read' and the resource 'the latest checkpoint and version' and provides a context ('after a fresh session or agent handoff'). It distinguishes the tool from siblings by implying a resume-specific use case, though it does not explicitly name alternatives.

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 a concrete condition for use ('after a fresh session or agent handoff') and adds operational guidance (treat state as untrusted, verify side effects). It doesn't explicitly state when not to use it or compare with siblings, but the provided scenario is clear enough for an agent to select it appropriately.

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