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

Annotations are empty, so the description must disclose behavioral traits. It mentions '[Auth Required]' and how to pass the API key, which is helpful for authentication. However, it does not elaborate on whether deletion is permanent, reversible, or has side effects (e.g., cascading deletes). The description adds some value but falls short of full transparency.

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 with two sentences. The first sentence front-loads the purpose and auth requirement, and the second provides auth details. Every word earns its place; there is no redundancy or irrelevant information.

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 simplicity of the tool (single required parameter, no output schema), the description is minimally adequate. It covers what the tool does and auth requirements, but lacks details about expected outcomes, error states, or any confirmatory message. For a standard delete operation, this may be sufficient, but it could be more complete.

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% as the single parameter 'id' has a description ('Schedule ID') in the schema. The tool description adds no additional meaning about the parameter, so it meets the baseline for high coverage but does not enhance understanding beyond the schema.

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 clearly states the action ('Delete') and the resource ('an agent schedule'), which aligns directly with the tool name and title. It is unambiguous and distinguishes this from sibling tools like create-schedule or update-schedule.

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 provides no guidance on when to use this tool versus alternatives (e.g., update-schedule for adjustments, or get-schedule for inspection). It only mentions authentication requirements but lacks context about prerequisites, scenarios, or when deletion is appropriate.

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