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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, openWorld), and the description adds genuinely new behavior: bytes are verified against stored size and digest before return, default is metadata-only, and returned filenames/media types/bytes must be treated as untrusted (a prompt-injection warning). It also clarifies that integrity means server-side hashing, not content review.

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 core capability and the conditional trigger before the security caveat. No filler or restatement of the title.

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?

With no output schema, the description adequately sketches the return (metadata vs. canonical base64 bytes with integrity guarantees) and the trust posture. It does not enumerate which metadata fields appear or error behavior (e.g. not-found, non-public artifact), leaving a small gap for a read tool.

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 coverage is only 50% (artifact_id is undocumented), so the description must compensate, and it does for include_content by explaining the verification step that gates byte return. artifact_id semantics remain unstated, but its meaning is self-evident from the tool name.

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 precise verb+resource ('Read public immutable artifact metadata') and immediately scopes the optional byte payload to include_content=true. This cleanly separates it from siblings like list_artifacts and upload_artifact without ambiguity.

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 conditional 'only with include_content=true' tells the agent exactly when bytes are returned versus metadata-only, which is the key invocation decision. It stops short of naming alternatives or stating exclusions (e.g. when to prefer list_artifacts, or behavior on missing/unpublished artifacts), so it is context-rich but not exhaustive.

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