mail_search_snippets

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

No annotations provided, so description carries full burden. It describes the output (subject with highlights, preview snippet) but does not disclose if it is read-only, any side effects, permissions needed, or rate limits.

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?

Description is reasonably concise: a purpose sentence, output format mention, sibling reference, and an arg list. Front-loaded well. No unnecessary fluff.

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?

The description is ambiguous about the relationship between required email_ids and the optional filter parameters. It says 'matching a filter' but requires email_ids, implying inconsistency. Does not clarify if filters are used for highlighting or for selecting emails. Output schema exists, so return format is covered, but usage context is unclear.

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 description coverage, the description adds brief explanations for each parameter (e.g., 'List of email IDs', 'Full-text search query') that go beyond the schema's type and title. However, explanations are minimal.

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 it gets highlighted subject/preview snippets and mentions the output format with <mark> tags. Relates to sibling mail_search_emails, but does not explicitly distinguish when to use one over the other.

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?

Says to use same filter params as mail_search_emails, implying a relationship, but does not explicitly state when to use this tool versus alternatives or any prerequisites.

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