get-mail-tips

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

The description describes a read operation ('Get the MailTips'), but annotations mark destructiveHint=true, creating a contradiction. No explanation of side effects or authorization beyond mentioning POST method.

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?

Front-loaded with core function, includes a helpful tip section, but is somewhat verbose with the body example and usage scenarios. Overall well-structured.

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?

Covers input, output, and usage adequately. However, the annotation contradiction undermines completeness, and no output schema means description must fully describe return values, which it does partially.

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?

The description adds detailed explanation of the body parameter format, including all MailTipsOptions enum values and their meaning, compensating for the schema's lack of description on the body parameter.

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 it retrieves MailTips for recipients, answers specific pre-send questions, and distinguishes from message retrieval and sending 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?

Explicitly advises using before sending emails to check OOF, mailbox quota, etc., and provides a specific usage scenario. Does not explicitly state when not to use, but context is clear.

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