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

Annotations already declare read-only, idempotent, non-destructive, closed-world behavior, so the safety profile is fully covered elsewhere. The description adds that the artifact's metadata is inspected, but says nothing about behavior on a missing or malformed artifact_id, permissions, or staleness of metadata.

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?

One front-loaded sentence with the verb first and no filler; the field list is dense but each item earns its place by previewing what is returned. Slightly list-like but efficient.

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 and rich annotations mean the description needn't explain return shape or safety, and it correctly focuses on when to inspect. However, it omits the required argument entirely and gives no indication of behavior when the artifact is absent, which is the remaining meaningful gap for a single-parameter lookup.

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?

The sole parameter, artifact_id (uuid), has 0% schema description coverage, and the description does not mention it at all — no clarification of where the id comes from or what format is accepted beyond the schema's uuid hint. With only one parameter, a brief note would have closed the 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 ('Inspect') and enumerates the metadata it returns (kind, units, checksum, lineage, mesh metadata), which makes the tool's scope concrete. It does not distinguish itself from near siblings such as get_artifact_download or read_artifact_summary, so it stops short of a 5.

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?

'before using it downstream' implies a pre-flight validation use case, which is useful timing guidance. It never names an alternative tool or states when to prefer a download or summary view instead, leaving the agent to infer sibling routing.

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