Cancel service

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

Annotations already mark it destructive; description adds concrete behavioral details: immediate vs scheduled execution, module deprovision when use_module is true with 'now', cron execution for scheduled cancellations, and the undo path via blesta_call services/unCancel. No contradictions with annotations.

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?

Three sentences, front-loaded with the core action, then the `when` breakdown, then the undo note. No filler; every sentence carries operational value.

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?

Given the 5-parameter schema and destructive annotation, the description covers timing, deprovisioning, and reversibility. It doesn't describe the return value (no output schema), but that's not required. Slightly more explicit guidance on when to prefer suspend_service would round it out, but the description is sufficient.

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 covers 4 of 5 parameters; description goes beyond by explaining the meaning of `when` options (default safest, immediate module deprovision) and ties `use_module` to the 'now' behavior. It doesn't add to service_id, but that's clear from context.

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 'Cancel' with resource 'service' and enumerates three timing options. Distinct from sibling suspend_service/unsuspend_service by the permanent cancel semantics. The 'Wraps Services.cancel' line anchors it to a known API.

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 clear context on what the tool does and the safest default for `when`, but doesn't explicitly contrast with suspend_service or specify when to choose this over alternatives. The exclusion of temporary suspension is implied by the name and sibling list, not stated.

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