Search Messages

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

Annotations already establish read-only, idempotent, and non-destructive behavior. The description adds that search is by text content and/or time range but does not disclose cross-space search behavior, pagination, or result limits beyond what the schema already lists. No contradiction with annotations.

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, front-loaded sentence with no filler or redundancy. It clearly states the action, resource, and search dimensions in minimal space.

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 the rich parameter schema, output schema, and annotations, the one-line description is mostly sufficient for an agent to invoke the tool correctly. The only notable gap is that it does not explicitly mention cross-space search behavior when space_id is omitted, but the max_spaces parameter description largely covers that.

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 description coverage is high (83%), with detailed documentation for query, space_id, page_size, max_spaces, and time_filter. The description adds little parameter-level meaning beyond naming the text-content and time-range search modes, so the baseline of 3 is appropriate.

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?

Description uses a specific verb ('Searches'), a clear resource ('messages in Google Chat spaces'), and explicit scoping ('by text content and/or time range'). This distinguishes it from siblings like search_gmail_messages and get_messages without requiring schema inspection.

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 gives no guidance on when to use this tool versus alternatives such as get_messages or search_gmail_messages. There are no explicit exclusions or routing hints, so an agent must infer the right context from the tool name and schema.

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