delete_billing_alert

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

Confirms destructiveHint annotation with 'Low blast radius and easily re-created' context. Describes confirm-gated behavior and that it makes no API call if confirm is false or omitted.

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?

Three concise sentences front-loaded with purpose, requirements, behavior, and usage. 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 purpose, permissions, confirmation flow, and singleton nature. Lacks description of return value on success, but given simplicity and destructive hint, this is a minor gap.

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 covers 100% of parameters with good description. Description adds that the alert is a singleton and that confirm must be user-approved, providing extra context beyond 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?

Clearly states 'Remove the month-to-date spend alert', a specific verb+resource. Mentions it's a singleton, distinguishing from other delete tools, and references sibling set_billing_alert.

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 says requires scope billing:write, explains confirm parameter usage with approval requirement, and notes the alert is easily re-created via set_billing_alert, providing alternative context.

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