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

No annotations are provided, so the description carries the full behavioral burden. It does not disclose what 'latest' resolves to during concurrent writes, whether retrieval requires authorization for specific artifacts, whether the version number in a response is returned, or any error behavior when an artifactId does not exist. For a read tool with zero annotation coverage it is thin.

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?

A single well-formed sentence with the operation front-loaded. It is efficient, though slightly under-elaborated for an endpoint whose parameters need explanation.

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 annotations, no output schema, and 0% schema description coverage, the description should carry far more: behavior of the default (latest), version semantics, error cases, and return shape are all absent. It is too sparse for a two-parameter retrieval tool whose parameters are undocumented elsewhere.

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 schema documents neither parameter beyond type and range. The description only vaguely gestures at 'version' via 'immutable version' but does not explain that omitting it yields the latest, nor what artifactId format is expected. It fails to compensate 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 (retrieve) and resource (artifact) and adds scope: latest version by default or a specific immutable version. This cleanly distinguishes it from the sibling artifact_put, which is the write counterpart. An agent can route between them 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?

The phrase 'or a specific immutable version' implies version selection but never explicitly states the selection condition (e.g., omit 'version' for latest, supply it for a pinned version) or when to prefer one over the other. No exclusions or alternatives are named. Usage is inferable but not spelled out.

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