spamtitan_delete_message

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

Description adds value beyond annotations: explicitly labels action as 'DESTRUCTIVE — IRREVERSIBLE', states permanence, and confirms removal from quarantine storage. Annotations already have destructiveHint=true, so the description reinforces and adds confirmation requirement without contradiction.

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?

Extremely concise: two short sentences plus an emoji warning. Critical information (destructiveness, permanence, confirmation requirement) front-loaded. No unnecessary words.

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 simple destructive tool with one parameter and no output schema, the description covers all necessary context: action, resource, irreversibility, and user confirmation. Sibling tools provide alternative actions, but the description is sufficient for this tool.

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% for the single parameter 'message_id', so the description does not need to explain parameters. The description does not repeat or enhance parameter meaning, which is adequate given high 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?

Tool name 'spamtitan_delete_message' combined with description 'Permanently delete a quarantined message by ID' clearly specifies verb (delete) and resource (quarantined message). Distinguishes from siblings like 'spamtitan_release_message' which implies a different action.

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?

Description includes explicit instruction to 'Confirm with the user before invoking', providing usage context. However, it does not explicitly state when not to use or mention alternative tools, but the warning implies cautious invocation.

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