mailkite_cancel_enrollment

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

Annotations already communicate destructiveHint, idempotentHint, and non-read-only behavior, so the description gets credit for adding the API key requirement and clarifying the scoped, per-run action. However, it does not describe side effects such as whether cancellation is reversible or what happens to related records.

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 short sentences, each earning its place: the main action and context, the alternative, and the auth requirement. Key information is front-loaded before branching to the alternative.

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 destructive action with strong annotations, the description covers the core usage scenario, the alternative tool, and credential requirement. It is slightly incomplete in that it does not mention the expected result or effect, but this is minor for such a simple call.

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?

The schema only says 'Path parameter id', but the description clarifies that the id is the enrollment id specifically targeting one run. This adds meaningful semantics over the bare schema for a single-parameter tool.

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?

Description states a specific verb ('Cancel'), a precise resource ('one specific run by its enrollment id'), and explicitly frames it as the per-row enrollments-table action. It also distinguishes itself from the sequence-level stopSequence alternative, making the purpose unambiguous.

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?

Explicitly tells the agent when to use this tool: for a single run from the enrollments table. It also names the alternative path for when the run is unknown ('use stopSequence') and contrasts the two conditions clearly.

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