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

With no annotations, the description carries the full burden and does disclose meaningful safety behavior: preview-by-default, no-retry intent, and post-readback verification. It also states the financial-booking exclusion. It does not explain permissions, irreversibility if preview is disabled, or exactly what "durable no-retry intent" means, so it is strong but not complete.

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 compact sentences with the safety condition and the core action front-loaded. Every sentence adds operational information, and there is no wasted phrasing.

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?

The output schema means return values need not be explained, and the description covers the destructive safety model well. However, with no annotations and 0% schema coverage, the missing parameter semantics and permission/irreversibility details leave material gaps for a destructive 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?

Schema description coverage is 0% across five parameters, and the description does not define kind, rule_id, company_name, or operation_key. "Default preview" implies dry_run and "exact" weakly maps to rule_id, but most parameter meaning is left undocumented.

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 gives a specific verb and resource: "Delete one exact AI rule." It also scopes the action with "only on an explicit user business instruction" and distinguishes it from financial booking deletion with "Never deletes a financial booking." An agent can identify the exact resource and the boundary of the operation.

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?

It states the condition for use ("only on an explicit user business instruction") and the default safety behavior ("Default preview"). It does not name a sibling alternative such as update_ai_booking_rule or audit_ai_booking_rules, so it is clear but not fully comparative.

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