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

Annotations already declare it is a non-read-only, non-idempotent, open-world write with destructiveHint=true, so the safety profile is covered. The description adds that the ticket is opened for a customer and scheduling is optional, but says nothing about side effects, duplicate creation on retry, or what happens when no service_date is supplied. It does not contradict the write annotations, though 'opens' sits uneasily with destructiveHint=true.

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 arguably under-specified rather than genuinely concise.

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?

This is a six-parameter mutation with no output schema, and the description never says whether the new ticket (and its identifier) is returned, nor what happens if customer_id is invalid. Given the destructive/non-idempotent annotations, an agent needs more than one sentence to invoke this safely.

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 83%, so the schema already explains project_id, customer_id, description, service_date, and service_time. The description only restates the optional date/time, adding no format or constraint detail beyond the schema; baseline 3 applies.

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 ('Opens a service ticket') plus the scope of the optional scheduling. An agent can tell it creates a service ticket rather than fetching or listing one, though it never names the creation-vs-update siblings (create_work_order, create_lead) explicitly.

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 instead of create_work_order, create_lead, or create_project, and no preconditions (e.g. that customer_id must come from list_contacts). The word 'optionally' hints that scheduling is not required, but nothing tells the agent what conditions select this tool.

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