save_gmail_draft

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

No annotations provided. Description only states it never sends and returns draft id. Missing details: overwrite behavior, permissions, rate limits, thread_id usage for replies.

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, front-loaded with key action and side effect. Could be slightly expanded to cover parameter roles without losing conciseness.

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?

Tool has 4 parameters, optional thread_id, and an output schema. Description omits crucial context: reply vs new draft, thread_id function, limits, and response details.

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 coverage is 0% (no parameter descriptions). The description does not explain any parameter beyond their names. 'thread_id' is especially ambiguous.

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?

Verbs 'Save' and 'never sends' clearly define the action. Resource 'Gmail DRAFT' is specific. Differentiates from siblings like fetch_emails (read) and write_report (different output).

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 explicit when-to-use or when-not-to-use guidance. No mention of prerequisites like authentication or Gmail account. No comparison to alternatives.

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