delete-focused-inbox-override

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

Description explains consequence: 'Future messages from that sender revert to the Outlook ML classifier's default behavior', adding behavioral context beyond annotations (destructiveHint=true). No contradictions with annotations.

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 efficient sentences: first states purpose, second provides actionable tip. No redundant words, fits context perfectly.

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?

Given simple deletion tool with annotations, description covers purpose, prerequisite, and behavioral effect. No output schema needed. Complete for agent understanding.

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 coverage is 100%, baseline 3. Description does not add meaning beyond the schema parameters (e.g., ID is mentioned but already in schema). No additional parameter elaboration.

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?

Description clearly states 'Delete an override specified by its ID' with specific resource ('Focused Inbox override') and verb, differentiating from sibling delete tools like delete-mail-message or delete-calendar-event.

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?

Provides explicit tip 'Use list-focused-inbox-overrides to find the ID first', guiding prerequisite usage. Does not contrast with update or create siblings, but still offers clear context for when to invoke.

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