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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds only a vague mention of filters and pagination, without saying what is returned, how paging works, or any rate/scope limits, so it adds little beyond the structured fields.

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?

One front-loaded sentence with no wasted words. It is efficient, though its brevity here is part of the under-specification problem rather than a virtue in itself.

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?

A 16-parameter search tool with no output schema and no parameter descriptions needs substantially more than one sentence. Nothing tells the agent which filters combine, how paging tokens work, or what a result contains, making the definition inadequate for the tool's complexity.

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?

There are 16 parameters with 0% schema description coverage, and the description does not name or explain a single one. With zero structured documentation, the description must carry the burden and it fails completely; an agent cannot tell what 'to', 'read', 'rawProviderQuery', or 'includeSearchContext' do without guessing.

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?

States a specific verb ('list or search') and resource ('mail') plus the general mechanism ('filters and pagination'). It does not differentiate from siblings like get_email, get_thread, or modify_emails, so it remains inferable rather than explicit, but the core purpose is clear.

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?

No guidance on when to use this tool versus get_email, get_thread, or list_folders, and no mention of prerequisites or account context. 'With filters and pagination' describes the mechanism, not when to choose this tool.

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