delete_alert_policy

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

No annotations provided, so description carries the burden. It discloses that the action removes a custom policy and reverts to default, indicating mutation. However, it lacks details on permissions, permanence, or restrictions (e.g., cannot delete default policies).

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 very concise, with a clear purpose, structured Args section, and relevant examples. Every sentence adds value; no unnecessary text.

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 a simple tool with one parameter and no output schema, the description covers the main action, effect, and parameter source. Could mention that only custom policies are affected or that the deletion is irreversible, but overall sufficient.

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?

With 0% schema coverage, the description explains the parameter 'policy_id: The ID from list_alert_policies()', which adds meaningful context beyond the schema's type and title.

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 'Remove a custom alert policy' with the effect 'revert to the default threshold.' The verb 'remove' and resource 'custom alert policy' are specific. Sibling tools like 'set_alert_policy' and 'list_alert_policies' are distinguished by the action and result.

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 explains that the policy_id should come from list_alert_policies() and provides examples. It implies usage for reverting to defaults but does not explicitly contrast with alternatives like 'set_alert_policy' for modifications.

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