iptime_cancel_change

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

Annotations provide the basic safety profile (non-read-only, non-idempotent, non-destructive), but the description adds no behavioral context. It does not explain what cancellation does to the plan, whether it is reversible, whether authentication is required, or what side effects may occur. The word 'cancel' is the sole behavioral clue.

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, complete sentence with no filler. It front-loads the verb and resource, and every word 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 one-parameter cancellation tool, the description is minimally viable: it names the action and the pending precondition, and the annotations cover the safety profile. However, it says nothing about the return value, error conditions, or whether the plan must belong to the current session, leaving minor but real gaps.

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%, and the description does not mention plan_id at all. While the parameter name is self-explanatory and the action implies it identifies the plan to cancel, the description does not explicitly state its role, leaving the agent to infer the connection.

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 uses a specific verb ('Cancel') and a specific resource ('pending change plan'), making the tool's function immediately clear. It also distinguishes itself from sibling tools like iptime_plan_change and iptime_apply_change by targeting a different stage in the change lifecycle.

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 description offers no guidance on when to use this tool versus alternatives. It does not reference siblings, prerequisites, or conditions such as 'use only if the plan has not been applied yet.' The only hint is the word 'pending,' which is too implicit to count as clear usage guidance.

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