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

Annotations already declare readOnlyHint, non-destructive, idempotent, and closed-world behavior. The description adds valuable behavioral context beyond annotations: reading in base64 chunks, rechecking bundle readability, and verifying exact version membership on every read.

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 front-loaded and compact: it first states the action, then explains first-read and continuation behavior, then notes revalidation. It is appropriately sized for a chunked file-read tool with little wasted text.

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?

The tool has annotations, a full schema description coverage, and an output schema, so the description does not need to explain return values in detail. It supplies the key chunking and continuation semantics an agent needs to call the tool correctly.

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 each parameter. The description still adds useful linkage semantics: the first read resolves directories/SPA fallback, while continuation reads use the returned versionId, exact path, and nextOffset as offset.

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 and resource: read complete file bytes from a bundle as base64 chunks. It is clear what the tool does, though it does not explicitly distinguish itself from similar sibling tools such as artifact_get_content or bundle_get.

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 explains continuation usage by saying to use the returned versionId, exact path, and nextOffset for subsequent reads. However, it does not state when to use this tool instead of alternatives or what prerequisites apply to the first read.

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