Archive one Gmail thread

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

Reveals the core behavior (removing INBOX label) despite no annotations. Missing details on permissions, side effects on other labels, or response format.

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?

Single sentence with clear action and ancillary usage note. No wasted words.

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?

Covers what, how, and where to get input, but omits error conditions, handling of optional parameters, and distinctions from similar 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 description coverage is 0%; description does not explain accountAlias or chatScope parameters. Only threadId is implied via usage guidance. Barely adds meaning beyond schema.

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?

States explicitly that it archives a Gmail thread by removing the INBOX label, and ties it to specific parameter sources. Clearly distinguishes the action and resource.

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?

Provides guidance on sourcing the threadId from fetch, followup_due, or get_thread, but does not differentiate from the sibling 'archive' tool or specify when not to use this tool.

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