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

Annotations already declare readOnly, idempotent, and non-destructive. The description adds real behavioral context beyond them: results are text-only (binary artifacts presumably unsupported) and size-capped, warning the agent about truncation. It omits the actual cap value and any error behavior for a missing hash.

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?

A single, front-loaded sentence with no filler; the constraints are packed into a parenthetical rather than padding the 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?

For a simple one-parameter fetch with no output schema, the description covers the essential caveats: text-only output and a size cap. It could be more complete by stating the cap and what happens when a hash is unknown or the artifact is binary.

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?

With one required parameter and 0% schema description coverage, the description carries the burden but only names the key (sha256) without format details such as hex length. It adds marginal value over the bare schema property name.

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?

States a specific verb (Fetch), resource (output artifact), and the identifying key (sha256), so the agent knows exactly what it retrieves. It does not, however, distinguish itself from siblings like fetch or get_execution, so it falls short of a 5.

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?

No guidance on when to use this versus the sibling fetch or get_execution tools, nor any prerequisites (e.g., where a sha256 comes from). Usage is only implied by the presence of the sha256 parameter.

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