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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds real value with "Hashes check bytes, not runs" — a semantic warning about what the hash actually proves — but leaves key behavior unexplained, such as what "availability" means (cached, signed, expiring URL) or whether the URLs are time-limited.

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 tight sentences with no filler, and the returned fields are front-loaded. The second sentence is terse to the point of being cryptic, but it is short enough to earn its place as a caveat.

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?

An output schema exists, so return values need not be spelled out, and the annotations cover the read-only nature. What remains missing is essential: the accepted form of the "artifact" argument and any reconciliation of the tool's name with its artifact-metadata behavior, both of which an agent needs before calling it.

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% and there is one required parameter, "artifact," whose format is never clarified — it could be an ID, a path, or a URL. Since the schema carries no meaning here, the description needed to compensate and does not.

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 has a specific verb ("Get") and concrete outputs (hosted-file URLs, SHA-256, availability) for an artifact, which is more than a tautology. However, it sits under the name "deployment_plan," which signals something quite different, and it never distinguishes itself from the several artifact-focused siblings (get_artifact, get_artifact_card, resolve_artifact). An agent can guess what it returns but not why it would pick this over those.

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?

There is no when-to-use statement and no named alternative, despite at least three sibling tools in the same artifact domain. The only guidance is the interpretive caveat "Hashes check bytes, not runs," which tells the agent how to read the hash rather than when to call the tool.

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