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

The annotations already communicate destructiveHint=true and readOnlyHint=false, so the description adds no new behavioral information. It fails to disclose the scope of destruction, particularly that an omitted queue_id results in deleting all queues for the profile. With no extra behavioral context beyond what annotations provide, this is a minimal score.

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?

'Delete schedule' is not merely concise; it is under-specified. It provides no usable structure or front-loaded decision cues. A two-word phrase that repeats the title is closer to missing content than to effective conciseness.

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 destructive operation, the description fails to convey the resource being affected (queue slot, schedule, or all queues) or the implications of optional queue_id. Although the output schema exists, the description leaves critical operational semantics to the agent to infer from the name and schema.

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 provides full documentation for both parameters, including the critical rule that omitting queue_id deletes all queues for the profile. With 100% schema description coverage, the description does not need to add parameter details, meeting the baseline.

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?

Tautological: description restates name/title.

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?

No guidance is given about when to select this tool over alternatives such as queue_update_queue_slot or queue_list_queue_slots. There is no mention of the critical behavior that omitting queue_id deletes all queues for a profile, which is essential for safe usage.

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