apply_thread_action

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

Adds context beyond annotations by mentioning dryRun, unreadOnly, syncBefore options. However, calling actions 'reversible' may mislead for destructive ones like delete, though destructiveHint is true.

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?

Three concise sentences: purpose, usage conditions, and supported options/alternatives. Front-loaded with key information, 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?

Given 7 params and no output schema, description covers purpose, usage, scope options, and alternative tool. Complete enough for an action application tool.

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 86%, and description adds value by explaining how dryRun, unreadOnly, and syncBefore affect behavior. Does not detail every parameter but compensates with high schema coverage.

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?

Description clearly states it applies a reversible mailbox action to every message in a thread, with examples (archive, mark-read). It also distinguishes from batch_email_action when using explicit emailIds.

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 says to use when acting on a full thread with threadId, and advises preferring batch_email_action for explicit emailIds, providing clear when-to-use and when-not-to-use guidance.

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