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

Annotations already cover readOnly, idempotent, openWorld and non-destructive behavior, so the description's added value is the fact that the URL is short-lived, the access is owner-scoped, and only manifest-listed artifacts resolve. It stops short of stating auth requirements, expiry duration, or what happens on a non-manifest key, so not 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?

Two sentences, zero filler: the return value and scope lead, and the disambiguation plus guardrail follow. Every clause carries 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 and 0% schema coverage on four parameters, so the description should do more than it does about runId/kind semantics and the URL's expiry. It is adequate for safe invocation (owners, manifest keys, prefer query tool) but leaves the parameter combinations largely inferential.

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% across 4 parameters, so the description must carry the load. It clarifies artifactKey must be manifest-listed (not arbitrary S3 keys) and enumerates some kind values indirectly, but never names artifactKey, runId, or deploymentId, and gives no guidance on how runId or kind interacts with artifactKey selection.

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") plus its scope, which cleanly separates it from query_deployment_artifact without opening either schema.

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 routes the agent to the sibling tool for tabular artifacts (agent_detail, memory, indicators, stats) "when the user needs analysis rather than a raw download," and adds the hard exclusion "never pass arbitrary S3 keys." Both when-to-use and when-not are stated.

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