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

Annotations only declare the mutation/safety profile (readOnly=false, destructive=false, non-idempotent); the description adds that the case is created without asking for confirmation and that the customer is answered through a separate channel — non-obvious behavioral facts. It also discloses the default 2-day deadline and that attachment links originate from mail_attachment_get, adding integration context. It does not say what happens on duplicate calls despite idempotentHint=false.

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 dense sentences that lead with the action and the created artifact, then the confirmation/customer-response caveat. Nothing is filler, though the trailing 'Works on: Support desk.' is terse and its meaning is not self-evident.

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?

An output schema exists so return values need not be explained, but with 10 parameters, a nested customer object and near-zero schema coverage, the description leaves too many inputs undefined for an agent to fill the call confidently. The core creation flow is covered; the surrounding parameter semantics are 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?

Schema coverage is only 10% (only 'account' is documented), so the description must carry the load. It does map a few parameters: description text, attachments as photo links from mail_attachment_get, assignee as 'responsible person', and due_days as the 2-day deadline — but product, customer (nested name/email/phone), order_ref, thread_id and purchase_date remain unexplained in both places.

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 and resource ('Open an internal warranty case: a task...') and enumerates what the created artifact contains (description, photos, responsible person, 2-day deadline). The scope note 'an internal task' distinguishes it from customer-facing responses and from courier_claim_open in the sibling list.

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?

'Created without asking (an internal task), the customer is answered separately' implies the context of use and that confirmation is not required, which is genuinely useful routing information. However, no alternative tool is named and no explicit when-not condition is given, so the agent must infer that courier_claim_open or callback_task are the wrong choices.

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