delete_schedule_time_range

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

Annotations already declare destructiveHint=true and readOnlyHint=false. The description adds the context that deletion is irreversible, which goes beyond the annotation. It also implies the target is a time range within a schedule, clarifying what is destroyed. No contradiction with annotations.

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 extremely concise: one sentence plus a warning. It is front-loaded with the action and resource, and every word adds value. The warning is prominent and appropriately placed.

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?

Given the rich schema (100% param coverage), annotations (destructiveHint=true), and output schema, the description is complete for a single-purpose delete tool. It covers the essential information (what is deleted and irreversibility) while leaving operational details to the schema. No critical information is missing.

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. The description adds only 'by ID' reference, which aligns with time_range_id but does not add additional meaning beyond the schema. The schema already documents confirm, dry_run, and apply_immediately sufficiently.

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 uses a specific verb ('Delete') and resource ('a time range from a firewall schedule') with the method ('by ID'). It clearly distinguishes from sibling tools like delete_firewall_schedule by specifying the scope as a single time range.

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 implies when to use the tool (delete a specific time range by ID) but does not explicitly mention alternatives or exclusions. For example, it does not state 'To delete an entire schedule, use delete_firewall_schedule instead.' The usage context is clear from the tool name but not elaborated with alternatives.

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