mail_search

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

No annotations provided. The description calls it a 'search,' implying read-only, but does not confirm safety, disclose side effects, or explain response behavior beyond parameter schema hints (e.g., returnPage changes output format).

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?

Two concise sentences: first states purpose, second gives usage guidance. No fluff, front-loaded.

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?

Despite 13 parameters and no output schema, the description is very brief. It does not explain return format, pagination, or what 'basic fields' encompasses. Agent needs more context to use effectively.

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 covers all 13 parameters with descriptions (100% coverage). The description adds no extra meaning beyond the name 'basic fields,' so baseline 3 is appropriate.

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 it is a 'convenience folder search by basic fields,' which specifies verb, resource, and scope. It distinguishes from sibling 'mail_search_advanced' by noting the latter offers richer filters and reliability.

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 to 'prefer mail_search_advanced for richer filters and agent reliability,' providing clear when-not-to-use guidance and directing to an alternative.

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