delete-focused-inbox-override

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

Annotations already indicate destructiveHint: true. The description adds that future messages revert to default behavior, but this is only marginal additional context. No contradiction 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?

The description is two sentences plus a TIP line. It is concise, front-loads the purpose, and uses bullet-style formatting effectively without waste.

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 delete operation with 4 parameters (1 required) and no output schema, the description explains the purpose, effect, and prerequisite. It does not detail the ETag usage for If-Match, but the schema covers that. Overall, it is sufficiently complete for basic use.

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%, so baseline is 3. The description only mentions the ID parameter ('specified by its ID') and does not add meaning to If-Match, includeHeaders, or excludeResponse.

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 clearly states 'Delete an override specified by its ID,' which specifies the action, resource, and parameter. The TIP further explains the effect on future messages, distinguishing it from other delete tools like delete-calendar or delete-mail-folder.

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 description includes a TIP that advises using list-focused-inbox-overrides to find the ID first, providing a clear prerequisite. It implies when to use this tool (to delete a focused inbox override) but does not explicitly state when not to use it.

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