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

With no annotations, the description carries full burden. It usefully discloses a side effect ('No reminder goes out for it') and hints at permission scope ('owner or office'), but says nothing about reversibility, whether the record is deleted or status-flagged, or what happens if the due date is already completed.

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 short sentences, front-loaded with the action and scope, followed by a use case and a side effect. No filler.

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 needn't be explained, and the tool is small. Still, for a destructive mutation with no annotations, the description should cover reversibility and precondition failure ('not open') to be complete.

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% for the single service_due_id parameter, so the description must compensate. It partially does by implying the ID must reference an 'open' due date, but never describes the ID format or where to obtain one.

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 ('Cancel an open service due date') with scope (open only) and actor (owner or office). This naturally separates it from sibling mutators services_addDue, services_completeDue, and services_updateDue, although none are named 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?

Provides one concrete usage scenario ('when the customer no longer wants the service'), which is genuinely helpful context. However, it gives no when-not guidance and never points at nearby alternatives such as services_updateDue (reschedule) or visits_cancel.

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