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

With no annotations provided, the description carries the full burden of behavioral disclosure. However, it only lists search criteria and does not disclose the return format, authentication requirements, or whether the operation is read-only. 'Search' implies a read operation, but the lack of explicit behavioral context is a notable gap.

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 a concise single sentence that front-loads the action ('Search Gmail') and requires no extra words. It earns its place with no fluff or repetition.

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?

For a search tool with no output schema and no annotations, the description is too sparse. It does not describe the return value, pagination, or the meaning of 'name' (sender vs recipient), and it omits guidance on when to use it relative to sibling tools like get_inbox. The missing 'limit' parameter semantics further reduce completeness.

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?

The schema has 0% description coverage, and the description adds some meaning by specifying 'name, subject, or keyword' as search inputs, presumably for the 'q' parameter. However, it fails to explain the 'limit' parameter or the exact syntax for 'q', leaving one of two parameters entirely 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 the tool's function: 'Search Gmail by name, subject, or keyword.' It uses a specific verb ('Search'), identifies the resource ('Gmail'), and outlines search criteria, which differentiates it from sibling tools like search_outlook and get_inbox.

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 implies usage for Gmail searches but provides no explicit guidance on when to prefer this tool over alternatives such as get_inbox or search_outlook. There is no mention of exclusions or alternative tools, so the context is inferred rather than stated.

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