search_threads

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

With no annotations, the description explains the multi-account behavior, search syntax, and return format. It is transparent about being a read operation, though does not mention authentication or potential side effects like 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?

Two sentences: first sets the multi-account context, second describes functionality with an example. No wasted words, efficiently front-loaded.

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 no output schema, the description explains 'compact thread summaries' which covers return values. It does not cover pagination details or account prerequisites, but schema handles parameter ranges and labels. Overall adequate.

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 coverage is 100%, so baseline is 3. The description adds value by explaining the search syntax and summarizing return format, enhancing meaning beyond schema parameter descriptions.

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 it searches email threads using full Gmail syntax, and the multi-account context distinguishes it from siblings like get_thread or archive_thread. Specific verb+resource combination with explicit scope.

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 searching within a single account but provides no explicit when-to-use or when-not-to guidance, nor mentions alternatives like get_thread for a specific thread.

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