Search Conversations

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

The description says 'Search messages' implying a read-only operation, but the limit parameter description reveals it may mark conversations as read, contradicting the readOnlyHint annotation. No disclosure of this side effect in the main description.

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 single sentence, very concise, but lacks important details. It is under-specified for a tool with side effects and sibling tools.

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 omits behavioral traits (marking as read), output format, and search scope, which are important given the existence of an output schema and sibling tools.

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% with good parameter descriptions (especially limit describing behavioral impact). The main description adds no parameter insight, so baseline 3 applies.

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 'Search messages by keyword' clearly states the verb (search) and resource (messages/conversations), but lacks differentiation from siblings like get_conversation or 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?

No guidance on when to use this tool versus alternatives such as get_inbox or search_people. The description provides no context for selection.

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