get_messages

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

Describes that sender names are resolved via People API and lists required OAuth scopes. However, it does not mention pagination behavior or rate limits. Since no annotations are present, the description carries the burden; it covers the most important behavioral aspects but lacks details on 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?

Description is concise with four sentences. Main action is stated first, followed by usage guidelines and behavioral notes. No unnecessary information.

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 tool has 5 parameters, required fields are stated, and output schema exists, the description covers purpose, usage, and key behaviors. Missing explicit details on pagination and default ordering beyond what schema provides, but largely sufficient.

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?

Input schema has 100% coverage with parameter descriptions. The description does not add additional meaning to parameters beyond what is in the schema. Baseline 3 applies as schema already provides parameter semantics.

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 clearly states 'List messages in a Google Chat space with sender names resolved' and specifies 'Use this to read a room/DM's recent messages'. It distinguishes from siblings like search_messages, send_message, and download_chat_attachment.

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?

Explicitly tells when to use this tool and when not, with alternative tool names: 'For text search across spaces use search_messages. For sending messages use send_message. For attachment downloads use download_chat_attachment.' Also mentions required OAuth scopes.

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