Search Mail

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

Discloses that it performs keyword-style lookups and can be constrained by time fields. Adds value beyond readOnlyHint annotation. Could mention return type limitation, but output schema covers that.

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?

Concise, front-loaded with purpose, then usage advice. No unnecessary words. Earns its place.

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?

Given 7 parameters, output schema exists, description covers core usage well. Could detail more parameters but still adequate for a search tool with good sibling differentiation.

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, description partially compensates by explaining query and filters parameters but does not cover limit, mailbox_id, or search_fields. Baseline is low, and description helps but not fully.

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 tool searches mail by literal query or fielded filters, and distinguishes from sibling tool mail_recent for chronological retrieval.

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 recommends mail_recent for chronological retrieval, advises asking for time window if missing, and suggests constraining with since/before. Provides clear when-to-use guidance.

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