Prepare exact artifact download

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

The description adds value beyond the readOnlyHint annotation by disclosing the 5-minute expiration and the privacy guarantee that stored bytes never enter MCP model output. These are not in the annotations and provide important behavioral context. 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 wasted words. The primary purpose is front-loaded in the first sentence, and the secondary behavioral note is in the second. Every sentence adds unique information.

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 tool's simplicity (3 UUID params, no output schema, good annotations), the description adequately covers purpose, expiration, and a privacy guarantee. It does not describe the return format (the URL), which could be useful, but overall it is sufficient for an agent to understand and invoke 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?

The input schema has 0% description coverage for its three UUID parameters, and the tool description does not explain any parameter semantics. The parameter names ('project_id', 'artifact_id', 'artifact_version_id') are self-explanatory, but the description could clarify that the version must be immutable (hinted) or how to obtain these IDs. It does not compensate for the missing schema descriptions.

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 tool creates a five-minute download URL for one immutable artifact version. It uses a specific verb ('prepare') and resource ('artifact download'), and distinguishes itself from siblings like 'prepare_artifact_upload' (upload direction) and 'get_artifact' (likely metadata retrieval).

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 implies use when an artifact version needs to be downloaded via a temporary URL, but it does not provide explicit guidance on when to avoid this tool (e.g., if the agent needs the artifact content directly in the model output) or mention alternative tools like 'get_artifact' for metadata. Usage context is clear but not contrasted with siblings.

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