delete_rule

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

No annotations are supplied, so the description carries the entire behavioral burden, and it says nothing about the operation being destructive and irreversible, what permissions are required, or what happens when the id does not exist. For a delete mutation with zero annotation coverage this is a substantive gap beyond what a reader can infer from the verb alone.

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?

A single short sentence with the operation front-loaded and the pointer to list_rules appended where it is most useful. There is no waste, though the extreme brevity leaves no room for the safety context a delete tool warrants.

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?

A destructive, one-parameter tool with no annotations and no output schema leaves the description responsible for safety and error behavior, yet none is covered. An agent knows what to call but not the consequences of calling it, which is incomplete for a delete operation.

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 0% description coverage, documenting only that id is a non-empty string. The description partially compensates by clarifying that id identifies an inbox rule and can be sourced from list_rules, but it adds no format, example, or error semantics for the parameter.

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 and resource ("Delete an inbox rule") plus the keying parameter ("by id"), which cleanly separates it from sibling mutators create_rule and list_rules. It stops short of full differentiation (e.g., no note on what happens to already-applied rules), but an agent can identify the operation immediately.

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 parenthetical "(see list_rules)" usefully tells the agent where to obtain a valid id, which is a real usage hint. However, there is no guidance on when deletion is appropriate versus alternatives (e.g., disabling or leaving a rule in place), and no prerequisites or preconditions are stated.

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