rws_comparison_save

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

Annotations already declare readOnlyHint=false, idempotentHint=true and destructiveHint=false, so safety profile is covered. The description adds genuinely useful context that inputs are referenced rather than moved, but says nothing about optimistic concurrency (expectedRevision), idempotency-key behavior (requestId), or what happens on conflict/upsert — meaningful 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?

A single front-loaded sentence with no filler. It is efficient, though slightly cryptic phrasing ('without moving their original producers') costs a little clarity.

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 deep nested schemas, revision control, an idempotency key, and no output schema, the description is under-specified. Critical operational facts (create-vs-update behavior, conflict handling, what is returned) are absent.

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 only 25% across four parameters. The record schema itself carries an update-semantics note, but the description adds no meaning for requestId (apparently an idempotency key) or expectedRevision (apparently optimistic locking), leaving the agent to infer their roles.

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?

The description names a specific verb and resource (save comparison inputs plus fixed/varying conditions) and clarifies the referencing behavior with 'without moving their original producers.' It is distinguishable from the many sibling *_save/*_register tools, though the phrasing is somewhat terse.

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?

There is no explicit when-to-use guidance, no mention of how this differs from the other save tools, and no stated prerequisites such as revision conflicts. Usage is only implied by the title-less name and the brief purpose sentence.

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