delete_notification

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

Describes the destructive action ('rule is gone') and return value. While no annotations are provided, the description adds context about permanence, but could more explicitly mention irreversibility or permissions.

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?

Front-loaded purpose, then alternative, then parameter docs, then return. Every sentence earns its place with no wasted 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?

Covers all essentials: purpose, alternative, parameters, return value. With no annotations, the description fully compensates, and the presence of output schema is covered by the return description.

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 0%, but description adds meaning for both parameters: explains account_id auto-resolves and notification_id is the rule ID. Could include more constraints (e.g., format) but sufficient for use.

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 'Delete a notification rule' with a specific verb and resource. It distinguishes from siblings like update_notification by providing an alternative.

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?

Explicitly tells when to use this tool vs. the alternative: 'to keep but mute it, prefer update_notification(send_email=False, send_desktop=False, send_push=False)'.

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