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

Annotations already declare readOnly=false, idempotent=true, destructive=true, covering the safety profile. The description adds genuine PATCH semantics ('omitted fields are left unchanged') and a scope limit, but says nothing about what the destructiveHint means in practice or what happens to concurrently edited fields.

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 sentences, front-loaded with the core action and scope, then the PATCH behavior. No filler; every clause earns its place.

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 10-parameter mutation with 0% schema description coverage and no output schema, the description is too thin. It omits per-parameter meaning, permission/state prerequisites, and any note on the destructiveHint, so an agent lacks enough to call it confidently.

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 0% across 10 parameters, so the description carries the full documentation burden. It only groups fields into carrier/driver/reference categories and does not map most parameters (notes, contactEmail, contactPhone, poReference) or explain formats, leaving half the inputs 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?

Specific verb (Edit) plus resource scope (appointment's carrier/driver/reference fields) with a strong qualifier '(no time change)' that separates it from reschedule_appointment. It does not name siblings explicitly, but the scope boundary is clear enough for an agent to pick it correctly.

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?

The '(no time change)' clause implies that time modifications belong to reschedule_appointment, and 'omitted fields are left unchanged' clarifies the patch usage. However, no alternative tool is named and no prerequisites (e.g. permission or state requirements) are stated, leaving usage largely implied.

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