delete_scheduled_message

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

Annotations already communicate destructive and non-idempotent nature. Description adds no further behavioral context beyond confirming deletion, which is acceptable but minimal.

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?

Very concise with the action upfront, but includes an unnecessary Args block that repeats the schema. Could be more streamlined.

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?

Output schema exists but description omits crucial context like irreversibility, prerequisites (message must be scheduled), and relationship to siblings like schedule_message or unsend_message.

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%, but description explains schedule_id as 'The ID of the scheduled message to cancel.' This adds meaningful context beyond the schema's type and title.

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?

Description clearly states 'Delete a scheduled message.' with a precise verb and resource, distinguishing it from siblings like schedule_message, unsend_message, and list_scheduled_messages.

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 on when to use this tool versus alternatives like unsend_message for sent messages or schedule_message for scheduling. Agent is left to infer context from tool names.

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