delete_self_notification

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

The description labels the operation as 'WRITE, destructive', which conveys mutability and potential irreversibility, but no annotations are provided to supplement. It lacks details on authentication, rate limits, or consequences beyond being destructive.

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, front-loaded sentence with no wasted words, effectively communicating the core action and key attributes.

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 one-param delete tool with no output schema, the description is minimally adequate but lacks context on error handling, idempotency, or return behavior.

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% with one parameter 'id' described as 'Self-notification UUID.' The description adds 'by ID' but provides no additional semantic meaning 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 verb 'delete' and resource 'self-notification', and specifies it operates by ID. It distinguishes from siblings like list_self_notifications, get_self_notification, and update_self_notification.

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 use when you need to delete a specific self-notification, but it does not explicitly state when to use vs alternatives, nor does it mention prerequisites or exclusions.

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