gmail_set_vacation

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

There are no annotations to convey safety or mutation hints, and the description merely says 'set' without disclosing side effects, authentication requirements, or behavior when toggling.

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 unambiguous sentence, but its brevity contributes to under-specification rather than conciseness, so a mid-range score is appropriate.

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 8 parameters and an output schema, this description is incomplete—it does not explain what the vacation responder does, how enable interacts with other fields, or what the response contains.

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 description coverage, the description provides no additional meaning for the 8 parameters; parameter names are self-explanatory but the description does not clarify required fields, defaults, or relationships like time windows.

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 uses a specific verb ('Set') with a clear resource ('Gmail vacation/auto-reply responder'), distinguishing it from sibling tools like gmail_get_vacation and gmail_send.

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?

No guidance is provided about when to use this tool versus alternatives, nor any context about prerequisites or intended use cases.

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