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

With no annotations, the description carries the full behavioral burden, and it does disclose the two most consequential traits: artifacts are immutable, and reusing artifactId chains versions instead of overwriting. It says nothing about required identity/permissions (agentId), content size limits (48k), or what happens on conflicting names, leaving real gaps for a mutation tool.

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 zero filler; the core action is front-loaded and the versioning rule follows immediately. Every clause earns its place.

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?

For a 7-parameter mutation tool with 0% schema description coverage, no annotations and no output schema, the description is too thin: it omits identity requirements, size constraints, metadata/mediaType behavior and the response shape. It covers the headline semantics but not enough for an agent to invoke it confidently.

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 7 parameters, so the description must compensate. It adds real meaning for artifactId (version chaining), workId (optional linkage) and content/mediaType ('text or structured content'), but agentId, name and metadata receive no explanation anywhere.

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 (Store) and resource (text or structured content as an immutable artifact version), and the phrase 'creates the next version' makes the write-and-version semantics unambiguous. It is clearly distinguishable from the artifact_get sibling and from the work_* tools.

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 description gives one concrete usage rule — reuse artifactId to append a new version rather than create a fresh artifact — which is genuine when-to guidance. It offers no explicit guidance on when to link a workId or when to prefer artifact_put over the other write tools (work_update, report_outcome), so usage is implied rather than spelled out.

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