hires_delete_notification_message

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

No annotations are provided, so the description carries the burden of behavioral disclosure. It states the core action and a limitation (cannot cancel sent messages), but does not mention reversibility, side effects, permissions, or error conditions. The description is functional but lacks depth expected for a mutating operation without annotation support.

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 two concise sentences, front-loaded with the verb 'Cancel'. Every word earns its place, with no redundancy or filler. It is a model of efficiency.

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?

Given the simplicity (one parameter, no output schema, no nested objects), the description sufficiently covers the tool's purpose and key limitation. It does not explain the return value or response behavior, but for a cancel/delete operation, this is often implicit. The description is adequate for a straightforward 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?

The schema already provides 100% coverage with a clear description for the only parameter ('Notification email message ID'). The tool description adds no additional meaning beyond what the schema states, so the baseline of 3 is appropriate.

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 uses a specific verb ('Cancel') and resource ('scheduled notification email'), clearly distinguishing it from general message deletion tools. The scope is well-defined: only scheduled emails before being sent. This is more precise than typical descriptions and differentiates from siblings like delete_message.

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 provides explicit when to use (before the email is sent) and when-not (already sent messages cannot be canceled). This is a clear exclusion that helps the agent decide between this tool and others. While alternatives are not named, the boundary is unambiguous.

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