alert_clear_all

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

With no annotations, the description must carry the full burden of behavioral disclosure. It simply states the action without indicating that clearing all alerts is likely destructive, irreversible, or affects all configured alerts. The agent has no information about side effects or whether confirmation is required.

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, concise sentence with no wasted words. While it is under-specified for a destructive operation, the conciseness itself is appropriate given the zero-parameter schema, though it could be slightly more informative.

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 destructive 'clear all' operation with no annotations and no output schema, the description is severely incomplete. It does not explain what 'alerts' refers to, whether the action is permanent, or what the outcome is. This is a significant gap that could lead an agent to invoke it without adequate understanding.

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 zero parameters, so the baseline is 4. The description correctly says nothing about parameters, and there is no need to compensate for missing schema documentation.

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 'Clear all alerts' uses a specific verb (clear), resource (alerts), and scope (all), making the purpose immediately clear. It implicitly distinguishes from sibling alert tools by specifying the 'all' scope, though it does not explicitly name alternatives.

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 no guidance on when to use this tool versus alert_delete, alert_pause, or others. There is no mention of prerequisites, scenarios, or cautionary notes, leaving the agent without direction for appropriate usage.

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