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

Annotations already declare readOnlyHint=true, so the safety profile is covered. The description adds real behavioral context beyond that: URLs are short-lived, access is owner-scoped, and only manifest-listed artifacts are reachable. It stops short of stating expiry duration or pagination/size limits, 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?

Three tight sentences, front-loaded with the output (signed URL), then the scoping constraint, then the alternative. No filler and each sentence adds distinct 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?

No output schema exists, but the description explains the return value (a signed URL) and its lifecycle, plus the key behavioral constraints. The main gap is undocumented runId/deploymentId semantics for a 4-parameter tool, otherwise an agent has what it needs to call it 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?

Schema description coverage is 0%, so the description must carry parameter meaning. It clarifies artifactKey (must be a manifest-listed key, never an arbitrary S3 key) and references several kind enum values, but leaves runId and deploymentId entirely unexplained. Partial compensation for the coverage gap.

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 and resource ('Returns a short-lived signed URL for one manifest-listed deployment artifact') and distinguishes it from query_deployment_artifact. An agent can tell exactly what this tool produces versus its nearest sibling.

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?

Explicitly names the alternative and the condition that selects it: 'Prefer query_deployment_artifact ... when the user needs analysis rather than a raw download.' It also states a hard constraint ('never pass arbitrary S3 keys') that governs correct usage.

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