rename-mailbox

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

No annotations exist, so description carries full burden. It warns that the operation renames a real folder and highlights case-sensitive matching. However, it does not detail other behaviors like effects on child folders or limitations.

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?

Extremely concise with 5 short sentences. Uses structured headings like 'Use when:', 'Returns:', 'Do not use when:', 'Safety:'. Every sentence adds value with no redundancy.

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 simple rename operation, the description covers the operation, return value, and safety. The output schema exists to describe the response. Could mention potential errors, but overall adequate.

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 only 33% (only account has description). The description adds context that oldName and newName are the names being changed and that oldName is case-sensitive, but it does not fully compensate for the missing parameter descriptions.

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 the action (renaming), the resource (mailbox/folder), and the scope (within an account). It explicitly distinguishes from sibling tools like create-mailbox and delete-mailbox.

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 guidance on when to use (renaming existing mailbox) and when not to (creating/deleting). Also suggests using list-mailboxes to confirm current name, offering context and alternatives.

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