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

With no annotations present, the description carries the full burden and does reasonably well: it discloses the auth requirement ('Requires files:write for API keys'), the optimistic-concurrency guard ('Refused if the file changed since the job started'), and that the result is written as a new version rather than overwriting. It does not describe the return payload or failure modes beyond the refusal case.

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 sentences, no filler, and the action plus the strongest precondition are front-loaded. 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 mutation tool with no annotations and no output schema, the description covers auth, the concurrency precondition and the write semantics, but leaves the three required parameters undocumented — a notable gap for a call that cannot succeed without correct UUIDs.

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 three required UUID parameters, and the description explains none of them. It conceptually links jobId and fileId ('a job's verified result ... of the file') but artifactBundleId is never mentioned, so the agent gets no guidance on what to pass.

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 ('Save') and a precisely scoped resource ('a succeeded deep compaction job's verified result as a new version of the file'), which distinguishes it from the generic update_artifact_file. It never names or contrasts with a sibling tool, so an agent must infer the boundary from context.

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?

Gives clear preconditions for use: the job must have succeeded and the file must not have changed since the job started. This tells the agent when the call will work, but offers no explicit when-not or alternative routing (e.g. rubrkit_update_artifact_file, rubrkit_apply_audit_rewrite).

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