outlook_delete_rule

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

With annotations absent, the description carries the full burden. It implies a destructive mutation but says nothing about irreversibility, required permissions, whether the rule can be recovered, or what happens if the ruleId does not exist. Only the mutation itself is conveyed.

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 seven-word sentence with the action front-loaded and zero filler. Nothing could be removed without losing meaning.

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 operation is intrinsically simple (one required ID, no output schema, no nested data), so the definition is minimally sufficient. However, for a destructive operation with zero annotation coverage it omits irreversibility and failure behavior, leaving real gaps.

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 100% and the single ruleId parameter is fully documented in the schema as "ID of the rule to delete." The description adds no syntax, format, or sourcing detail beyond that, so the baseline 3 applies.

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 states a specific verb ("Delete") and resource ("inbox message rule"), and the qualifier "by ID" signals the lookup key. The resource 'rule' is unique among siblings (delete_email, delete_event), so an agent can route correctly without opening the schema, though it never explicitly contrasts those siblings.

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?

No guidance on when to use this versus outlook_list_rules (to find the ID) or outlook_create_rule, and no prerequisites such as needing the ruleId from a prior list call. The agent must infer the workflow entirely.

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