compose_mail

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

Discloses main side effect (opens UI window) and non-sending behavior. Annotations provide readOnlyHint false, confirming mutation. No hidden behaviors mentioned.

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 with critical qualifier, front-loaded. No wasted words.

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?

Minimal but sufficient for a simple UI tool. Lacks info on prerequisites (e.g., mail app), return values, or error handling.

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 0% and description adds no parameter details. Parameter names are self-explanatory, but format, constraints, or usage notes are missing.

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?

Clearly states verb 'open' and resource 'mail compose window', explicitly noting it does not send. Differentiates from send_imessage and similar tools.

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?

Implies usage for composing email without sending, but lacks explicit alternatives or when-not-to-use guidance. The 'does not send' clause is helpful.

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