snooze

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

Discloses side effects (removes INBOX, adds a dated label), reversibility (via unsnooze), and dependency on sweep_snoozed. Adds value beyond annotations, which only indicate idempotent and non-destructive.

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 concise sentences with bullet points, front-loaded with core purpose. No unnecessary words; every sentence adds value.

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?

Containing purpose, usage guidelines, side effects, reversibility, and sibling relation, the description is complete for a tool with 2 parameters and an output schema.

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?

The description explains the 'until' parameter's format (YYYY-MM-DD) and purpose. The 'threadId' is not described but is standard and self-explanatory. Given 0% schema description coverage, the description compensates well.

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 the action ('Snooze a thread until a date'), specifies the verb (snooze) and resource (thread), and distinguishes from siblings by mentioning alternatives like archive or trash.

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 states when to use ('deferring a thread to a later date instead of leaving it in the inbox') and when not to use ('for permanent removal (use archive or trash)'), providing clear guidance and alternatives.

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