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

With no annotations provided, the description carries the full burden of behavioral disclosure. It says 'cancel or delete' which implies mutation, but it does not explain consequences such as whether the action is reversible, whether any notifications are sent, or if there are any prerequisites like permissions. The ambiguity between 'cancel' and 'delete' is also unresolved.

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?

The description is a single, concise sentence that conveys the essential purpose without any filler. It is appropriately sized for a simple tool with one parameter, and the information is front-loaded.

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?

While the tool is simple, the absence of annotations and output schema leaves gaps. The description does not clarify the distinction between canceling and deleting, nor does it mention side effects, required permissions, or what the response looks like. For a mutation tool, this is insufficient context.

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 100%, so the visitId parameter is fully documented in the schema with an example. The description does not add any semantic meaning beyond what the schema provides, which meets the baseline for a tool with full schema coverage.

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?

The description clearly states the action (cancel or delete) and the resource (scheduled appointment/visit) within the Jobber calendar context. This distinguishes it from sibling tools like jobber_schedule_visit, jobber_reschedule_visit, and jobber_get_visits, which are obviously different operations.

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 tool versus alternatives. It does not mention when cancellation is appropriate, whether it should be preferred over rescheduling, or any conditions that might make it unsuitable. The description simply states what it does without contextual usage cues.

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