Refresh Mail Snapshot

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

With no annotations aside from title, the description must disclose behavioral traits. It mentions 'temporary' and 'snapshot', suggesting a point-in-time copy, but does not elaborate on side effects, resource usage, or what happens to existing snapshots. This is adequate but lacks full transparency.

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?

The description is a single concise sentence without fluff. However, given the missing parameter explanation, it sacrifices informativeness for brevity. Still well-structured.

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?

For a tool with one optional parameter and no annotations, the description should cover the parameter and provide more context about snapshot behavior. It fails to do so, leaving the agent underinformed despite the existence of 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 ignores the sole parameter 'ttl_seconds', which is undocumented in the schema (0% coverage). It does not explain the parameter's purpose, leaving the agent to infer from the name and default. This is a significant gap for a tool with only one parameter.

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 verb 'Create', the resource 'temporary Mail metadata snapshot', and the context 'for fallback read workflows'. It effectively distinguishes this tool from sibling mail tools, which focus on reading, searching, or modifying messages directly.

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?

The phrase 'for fallback read workflows' provides clear context on when to use this tool, implying it is an alternative to normal read tools when they fail. However, it does not explicitly list alternatives or state when not to use it, leaving some guidance implicit.

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