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

Annotations already declare destructiveHint=true, readOnlyHint=false, and idempotentHint=false. The description adds meaningful behavioral context beyond this: non-empty schedules are refused with the offending deliverables named, the DS number is never reissued, and the operation is free on every tier. These details help agents anticipate failure modes and long-term side effects.

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 three sentences with no wasted words. The primary action and precondition are front-loaded, followed by refusal behavior and a long-term consequence. Every sentence earns its place, and the structure is clear and direct.

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 single-parameter destructive tool with full schema coverage and informative annotations, the description covers the essential operational context: what it does, when it fails, and the persistent effect of the deletion. It does not specify the success response format, but that is acceptable given the absence of an output schema and the simplicity of the operation.

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 input schema already describes the 'schedule' parameter with examples (DS-2026-0001, WO-2026-0001, or title), giving 100% coverage. The description does not add further parameter-level details, so the baseline of 3 is appropriate—the schema carries the semantic load.

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 states a specific verb ('Delete') and resource ('schedule') with a clear condition ('carrying no deliverables'), and distinguishes this tool from siblings by specifying it only applies to empty schedules. The alternative behavior for non-empty schedules is also mentioned, so an agent can tell this apart from related tools.

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 clearly indicates when to use the tool (to free an open slot by deleting an empty schedule) and when not to (if the schedule holds any deliverables, it will be refused). However, it does not explicitly name sibling alternatives, such as delivery_schedule_create or deliverable_delete, so it falls slightly short of the highest score.

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