fetch_artifact

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

With no annotations, the description carries the burden of disclosing behavior. It usefully reveals that the tool verifies the artifact hash, returns a local path, and only returns content when explicitly requested and bounded. However, it does not clarify what happens on hash mismatch, how 'bounded' is enforced, or whether network/IO side effects occur.

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 a single dense sentence with no fluff, and the primary purpose is front-loaded. The second clause is terse and somewhat ambiguous, but it still conveys the key content-related constraint without wasted words.

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 tool with no annotations, no output schema, and zero parameter descriptions, the description is too sparse. It gives the return type (local path) and a hint about content, but it omits selection criteria, artifact identification semantics, failure behavior, and precise limits, leaving the agent to infer too much.

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 compensate for parameter meaning. It adds some meaning for content and max_bytes ('content requires explicit true and is bounded'), but it does not explain how job_id and name identify the artifact, nor what units or limits max_bytes uses.

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 identifies a specific action—'Verify artifact hash and return its local path'—and a clear resource (artifact). It stops short of explicitly naming a sibling alternative like list_artifacts, but the verify-and-return-path wording differentiates it from listing operations.

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 is given about when to use fetch_artifact versus list_artifacts or other job-related tools. The only usage hint is that content requires explicit true and is bounded, which is more of a parameter behavior than tool-selection guidance.

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