List Gmail Sent folder (deprecated)

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

No annotations exist, so description must carry full burden. It only states 'lists the latest messages' without specifying ordering, count limit, or pagination. Lacks detail on what 'latest' means and does not disclose any restrictions beyond lack of filters.

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 covers deprecation and alternative, second covers basic function. Front-loaded but omits crucial parameter details, making it incomplete rather than concise.

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 3 parameters with no output schema or annotations, description fails to cover parameter semantics and behavioral details. Overall incomplete for effective tool usage.

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?

With 0% schema coverage, description must explain parameters. It mentions none of the three: maxResults, accountAlias, chatScope. No guidance on how they affect behavior.

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 the tool lists messages in Gmail Sent folder and identifies itself as deprecated, explicitly distinguishing from the preferred alternative multi_gmail_fetch. Verb 'list' and resource 'Gmail Sent' are specific.

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 says 'Deprecated — prefer multi_gmail_fetch with queryMode=raw and a Gmail query' and clarifies that this tool lacks date/query filters, providing clear when-to-use and when-not-to-use guidance.

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