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

With no annotations, the description should disclose behavioral traits. It merely states 'Save,' implying a mutation, but omits details like idempotency (despite idempotencyKey parameter), preflight requirements (consentDeclaration and runtimeDeclaration), or whether it overwrites existing revisions. Minimal disclosure.

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?

The description is a single short sentence, which is efficient. However, it could include slightly more context (e.g., the purpose of expectedVersion) without being verbose. No wasted words.

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?

Given the lack of output schema and the tool being a mutation within a workflow (presence of lock and map siblings), the description is incomplete. It doesn't explain what a placement revision is, how this save fits into the broader process, or what success/failure outcomes look like.

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 coverage is high (75%) and includes detailed descriptions for most parameters (workspaceId, outputFormat, idempotencyKey, input fields). The description adds no new meaning beyond what the schema already provides, so baseline score of 3 is appropriate.

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 states 'Save a placement revision,' which is a specific verb and resource. It clearly indicates the action and object, but lacks differentiation from sibling tools like lock_sulvo_placement_revision or map_sulvo_placement_backup.

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?

No guidance on when to use this tool versus alternatives is provided. The description only lists required inputs without any context about prerequisites, workflow position, or exclusions.

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