Mail Access Setup

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

Annotations are minimal, so description carries the burden. It transparently discloses the optional system settings opening, but doesn't detail potential side effects (e.g., user interaction required).

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?

Single sentence that is front-loaded with the main action. No wasted words; every part adds value.

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 utility with one parameter and an output schema, the description covers the tool's purpose and parameter. No missing critical context.

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?

With 0% schema coverage, the description compensates by explaining the 'open_settings' parameter's effect. It clearly ties the boolean to opening settings, adding value beyond the schema.

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 the tool explains Mail access modes and optionally opens Full Disk Access settings. This distinguishes it from all sibling tools, which focus on mail operations, diagnostics, or other preferences.

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 explicit guidance on when to use this tool versus alternatives. While sibling tools don't overlap, the description doesn't clarify contexts like troubleshooting vs. initial setup.

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