delete_notification

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only states the action and does not reveal important traits such as irreversibility (permanent deletion), permission requirements, or potential side effects (e.g., whether the notification is also removed from push history). The term 'Deletes' implies destruction, but no additional context is offered.

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, focused sentence that directly states the tool's purpose without any unnecessary words or filler. It is appropriately sized for the tool's simplicity and front-loads the core action and resource.

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 single-parameter delete operation, the description is largely complete: it identifies the action and the target. However, the absence of any mention of permanence or confirmation requirements leaves a small but real gap. Given the tool's low complexity, the description is sufficient for basic understanding but stops short of detailing the full behavioral context.

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?

The input schema has full 100% coverage: the only parameter 'notification_id' is described as 'Notification ID to delete'. The description adds no extra meaning beyond what the schema already provides, so a baseline of 3 is appropriate. No further elaboration is needed for this simple parameter.

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 'Deletes a specific notification' uses a clear verb (Deletes) and resource (notification), making the tool's purpose immediately obvious. It is specific and distinct from sibling tools like delete_message or delete_channel, which target different resources.

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 is provided on when to use this tool versus alternatives, prerequisites, or exclusions. The description simply states the action, leaving usage entirely implied. For example, it does not mention that this tool is for removing individual notifications as opposed to bulk deletion or that it only affects notifications, not messages.

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