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

Annotations already establish readOnlyHint=true and destructiveHint=false, but the description adds meaningful operational context: the resource is public and immutable, no authentication is needed, it contains no private Temple material, and integrity should be verified locally. It does not describe pagination or chunk-boundary behavior, keeping it below a 5.

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 efficient, with four short sentences that each contribute useful information. There is no redundant restatement of the name or annotations.

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 output schema and annotations cover return shape and safety, and the description explains the public/immutable/no-auth context. However, with 6 parameters and low schema coverage, it does not give an agent enough guidance on limit, offset, name, or release semantics to be fully complete.

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 only 17%, so the description must compensate. It explains the action modes (manifest, source text, ZIP chunks) and mentions pinning a release, but it leaves name, limit, offset, and account_ref unexplained, and it calls the parameter release_id while the schema names it release.

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 the public immutable pilot manifest, exact source text, or base64 ZIP chunks. It is clear enough to distinguish from most siblings, but it does not explicitly differentiate itself from the nearby eclypse_recovery_diagnostic tool.

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 useful usage context: no browser, account, provider key, or model call is required, and release_id should be pinned with SHA-256 verification locally. It does not explicitly state when to choose this over recovery_diagnostic or other siblings, so it falls short of full alternative guidance.

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