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

Annotations already declare readOnlyHint=false, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the description does not contradict them. However, it adds nothing beyond those hints — no mention of whether a draft is auto-numbered, what state it starts in, or what idempotency_key semantics actually mean in this domain.

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?

One sentence with no wasted words, but the brevity is under-specification rather than conciseness — it conveys no information beyond the tool name.

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?

A 10-parameter mutation with nested objects, zero schema description coverage, and no output schema leaves the agent with almost no basis for correct invocation. The description must compensate for that gap and does not.

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?

All 10 parameters sit at 0% schema description coverage, and the description mentions none of them. The agent gets no meaning for terms_json, content_ast, snapshot_html/text limits, template_version_id, packet_id, or why application_id and idempotency_key are required.

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 when-to-use guidance whatsoever — no prerequisites, no mention of when a draft is required versus updating an existing offer or opening a revision, and no routing among the many offers siblings.

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