List Gmail Sent folder (deprecated)

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

With no annotations, the description minimally conveys that the tool is a read operation (listing) without filters. It does not disclose pagination, rate limits, or return format, but for a simple list tool this is adequate.

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 efficient sentences with the most critical information (deprecation and alternative) front-loaded. Every word adds value; no fluff.

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 three parameters and no output schema, the description fails to cover parameter usage or return structure. It only states the basic functionality, which is insufficient for proper invocation.

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 0%, yet the description explains none of the three parameters (maxResults, accountAlias, chatScope). There is no guidance on what they do or how to use them, leaving the agent uninformed.

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 lists latest messages in Gmail Sent without filters. The deprecation note and reference to multi_gmail_fetch distinguish it from siblings, but the 'latest messages' phrasing is somewhat vague regarding sort order.

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 advises using multi_gmail_fetch with queryMode=raw and a Gmail query instead, and clarifies that this tool still works but lacks filtering. This provides clear when-to-use guidance and an alternative.

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