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

Annotations already declare destructiveHint=true, idempotentHint=true, and readOnlyHint=false, so the safety profile is covered. The description still adds genuinely new behavioral facts the annotations cannot convey: that past runs and their results survive the deletion (blast radius), that user confirmation is required, and that the call is free. Auth requirements and return shape are the only gaps.

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?

Four short clauses, each carrying distinct information: action, id provenance, blast radius, confirmation gate, and cost. Front-loaded with the operation and free of filler.

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?

An output schema exists, so return values need not be explained. For a single-parameter destructive tool, the description covers everything an agent needs before invoking: what is deleted, what is preserved, the confirmation requirement, and the id source.

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 100%, so the baseline is 3 and the schema already documents the id format. The description goes further by naming the tool that produces a valid id (procli_schedule_list), adding provenance the schema does not provide.

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?

Specific verb+resource ("Delete one schedule") that cleanly separates it from the sibling schedule tools (create/list). The scope qualifier "one" distinguishes it from any bulk operation, and the parenthetical id source removes ambiguity about what is being deleted.

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?

It tells the agent where the id comes from (procli_schedule_list) and adds an explicit pre-condition ("Confirm with the user first"), which is real usage guidance for a destructive call. It stops short of stating when-not-to-use or naming a competing tool, so it is not a full 5.

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