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

Annotations already flag destructiveHint=true and idempotentHint=false; the description adds the meaningful scope of destruction — that a bare cancel kills the entire window while skip-next only removes one occurrence. It does not state whether the cancelled window can be restored or what a non-repeating window cancel returns, so it adds context but not a full behavioral picture.

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 tight sentences, effect stated first, then the mode semantics — no filler and nothing repeated from the schema verbatim.

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 3-parameter destructive tool with full schema coverage and a rich annotation set, the description covers the purpose, effect, and the branching semantics of action. The remaining gap is disambiguating this from vs_maintenance_delete and vs_maintenance_update, which an agent must otherwise infer.

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 coverage is 100% (baseline 3), and the description goes beyond the schema by specifying the default behavior when action is omitted and by clarifying that skip-next/stop-repeating only apply to repeating windows. The occurrence parameter is left entirely to the schema, which is acceptable given full 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?

States a specific verb and resource ("Cancel a maintenance window") and adds the operational consequence ("so alerts flow again"), so the agent immediately understands the effect. It does not differentiate from the closely-named sibling vs_maintenance_delete, leaving ambiguity between cancelling/ending a window and deleting it.

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?

Gives explicit conditional routing among modes: "skip-next" for one occurrence, "stop-repeating" to end the repeat, and implicitly cancel the whole window when no action is given or the window doesn't repeat. That is clear when-to-use guidance for the action parameter, though it never says when to prefer vs_maintenance_delete or vs_maintenance_update instead.

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