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

Annotations already declare destructive=true and idempotent=true. The description adds useful behavior beyond that: the rule stops answering immediately and its activity remains available in list_auto_reply_activity for 90 days.

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?

Two short sentences with the core delete behavior front-loaded. The retention detail in the second sentence is useful and earns its place.

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 two-parameter delete tool with rich annotations and no output schema, the description covers the key behavioral consequences. It still leaves a gap around obtaining rule_id and does not clarify when to choose deletion over update/disable.

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 only 50%: workspace_id is described in the schema, but rule_id is undocumented in both schema and description. The phrase 'a rule' weakly maps to rule_id but does not explain its format, source, or lookup method.

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?

States a specific verb ('Deletes') and object ('rule'), plus the immediate effect ('stops answering at once'), which identifies the auto-reply deletion operation and separates it from list_auto_replies and update_auto_reply.

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?

There is no explicit when-to-use or when-not-to-use guidance, and no alternative is named. It does not address whether an agent should delete versus update/disable an auto-reply.

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