delete_reporting_rule

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

With no annotations provided, the description carries the full burden of disclosing behavioral traits. It explicitly notes that agents using the rule will be reassigned to the default rule, which is a valuable side effect beyond the schema. However, it does not mention any other consequences (e.g., irreversibility) or the confirm requirement, which are partially covered by the schema.

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 sentence with a parenthetical, immediately stating the action and its key effect. It is concise, front-loaded, and contains no filler, making it highly efficient.

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 simple delete operation with two parameters, the description covers the core action and the most important side effect. It lacks explicit information about return values or error handling, but given the absence of an output schema and the tool's simplicity, it is reasonably complete, though not exhaustive.

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 100% coverage with descriptions for both rule_id and confirm, so the description adds no additional parameter-level detail. It does not explain formats, valid values, or relationships beyond what the schema already provides, warranting a baseline score.

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 the specific verb 'Delete' with the resource 'reporting rule', clearly distinguishing it from sibling tools like create_reporting_rule, update_reporting_rule, and get_reporting_rule. The parenthetical about agents being reassigned to the default rule further clarifies the tool's scope and effect.

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 does not explicitly state when to use this tool over alternatives or provide exclusions. The parenthetical implies a scenario (deleting a rule that agents use), but there is no direct comparison with update_reporting_rule or other options, so usage guidance is only implied.

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