search_emails

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

No annotations provided, so description must convey behavioral traits. It mentions query syntax and sort options, but fails to disclose key details such as whether the tool is read-only, pagination behavior, authentication needs, or what happens if max_results is exceeded. The destructive/read-only nature is not addressed.

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?

The description is concise with minimal waste. It starts with the main purpose and immediately provides examples and parameter details. Front-loaded, but could be slightly more structured for readability.

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 4 parameters and an existing output schema, the description covers query syntax and sort options but misses max_results. No guidance on result format or pagination, though output schema may partially compensate. Overlooks usage context relative to siblings.

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 description coverage is 0%, so description must compensate. It explains sort_field and sort_order with defaults and valid values, and gives examples for the query parameter. However, max_results is not mentioned at all, leaving one of four parameters undocumented.

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 'Search emails using mu find query syntax', which is a specific verb+resource. The tool name search_emails is distinct from siblings like count_emails, get_email, find_contacts, and list_mailboxes, so purpose is well-differentiated.

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?

The description provides examples and explains sort fields/order, implying usage, but does not explicitly state when to use this tool versus alternatives like get_email or count_emails. No 'when not to use' guidance is given.

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