get_artifact_download_url

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

With no annotations, the description must disclose behavioral traits. It mentions 'temporary' and 'signed', key traits about URL lifetime and security. However, it does not specify expiration duration or whether multiple calls are safe. Adding 'temporary' and 'signed' is valuable but leaves some gaps.

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?

Single sentence, no redundant words. Each word adds value: 'Create', 'temporary signed download URL', 'for a managed job artifact'. Perfectly concise.

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 no output schema, the description should explain the return value (the URL) but does not. It is incomplete in that respect. However, it covers the core purpose and hints at usage via parameter descriptions. Needs to mention that the output is a downloadable URL.

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 has 100% description coverage for both parameters, so baseline is 3. The description adds no additional meaning beyond the schema's parameter descriptions (job_id is the job ID, artifact_id is from list_job_artifacts).

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?

Description clearly states it creates a temporary signed download URL for a managed job artifact, using a specific verb and resource. It distinguishes itself from sibling tools like list_job_artifacts (which lists artifacts) and get_job (which gets job info).

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 explicit guidance on when to use this tool vs alternatives. The schema hints at a dependency on list_job_artifacts for artifact_id, but the description does not mention this or provide any prerequisites or exclusions.

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