Update IMAP Auth Profile

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

Annotations already declare readOnlyHint=false, idempotentHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is covered structurally. The description adds nothing beyond that - it does not explain what 'settings' mutates, whether changes are reversible, or any permission requirements.

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?

It is a single short sentence, but that brevity stems from under-specification rather than disciplined conciseness. The label 'Purpose:' adds no structure or information.

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?

This is a mutation tool with no output schema and a nested, unconstrained 'settings' object, yet the description says nothing about what fields can be updated, what the domain/key scope implies, or what the result looks like. An agent cannot call it confidently.

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 the schema documents key, domain, and settings on its own, giving a baseline of 3. The description adds no meaning beyond that; notably the opaque 'settings' object with additionalProperties:{} is left entirely unexplained.

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 reads 'Purpose: Update IMAP Auth Profile,' which merely restates the tool name and title verbatim. There is no added specificity about what an IMAP Auth profile is or how this update differs from sibling operations like create or delete.

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 whatsoever on when to use this tool versus the many siblings (imap_auth.create, imap_auth.get, imap_auth.delete, smtp_auth.update). No prerequisites, no exclusions, no context.

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