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

Annotations already declare destructiveHint=true, idempotentHint=true, readOnlyHint=false, and openWorldHint=false, so the safety profile is covered. The description adds only a thin concurrency hint with using its current version, but does not explain what data may be overwritten, how conflicts are handled, or whether partial updates are supported.

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 sentence with no wasted words, but it is drastically under-specified for a 9-parameter destructive update operation. Conciseness here comes at the cost of clarity rather than efficient communication.

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 9 parameters, 0% schema description coverage, no output schema, and rich annotations, the description is far too sparse. It does not explain required parameters, partial versus full update behavior, concurrency failure handling, or the expected result of the operation.

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 9 parameters, and the description only vaguely corresponds to expected_draft_revision via current version. It provides no semantics for offer_id, idempotency_key, terms_json, content_ast, valid_until, snapshot_html, snapshot_text, or request_id, leaving nearly all parameters undocumented.

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?

Tautological: description restates name/title.

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 guidance on when to use this tool versus alternatives such as yardstick_offers_create, yardstick_offers_documents_edit, or other offer mutation tools. The phrase using its current version implies a precondition but does not explicitly state when this tool is appropriate or what to do if the revision is stale.

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