delete_scheduled

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

Annotations already disclose the destructive nature (destructiveHint=true) and non-idempotency (idempotentHint=false). The description adds the useful context that this operates only on messages before sending, which is a behavioral constraint. However, it does not elaborate on permanence, effects on multiple chats, or confirmation requirements beyond the 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 a single, concise sentence that front-loads the action and includes a helpful qualifier. There is no extraneous information or repetition of schema details.

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 simple operation, the presence of an output schema, and destructive annotations, the description is minimally adequate. However, it lacks parameter semantics and prerequisites (such as how to obtain scheduled message IDs), leaving gaps for an agent to invoke the tool correctly.

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 0%, and the description provides no information about the 'chat' or 'message_ids' parameters. While 'message_ids' can be inferred as scheduled message IDs from the tool's purpose, the 'chat' parameter is ambiguous (which chat? integer or string?). The description fails to compensate for the low schema coverage.

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 ('scheduled messages') with a temporal qualifier ('before they are sent'). This distinguishes it from the sibling tool 'delete_message' which likely targets sent messages, making the purpose unambiguous.

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 phrase 'before they are sent' provides clear temporal context for when to use this tool (for canceling unsent scheduled messages). While it doesn't explicitly name alternatives or exclusions, the context is effective and implies that this is not for deleting already-sent messages.

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