pause_automation_email

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

Discloses queuing behavior for subscribers, authentication method, rate limit, and respect for read-only/dry-run modes. Annotations are non-contradictory and description adds substantive behavioral details.

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?

Front-loaded with action, then details, then structured Args and Returns. Every sentence adds value with no redundancy.

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?

Covers action, queuing behavior, authentication, rate limit, modes, parameter explanations, and return value. Adequate for a mutation tool with provided annotations and 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?

Despite 0% schema description coverage, the description includes an 'Args' block explaining each parameter's purpose, including the optional account parameter and reference to list_accounts, adding significant meaning beyond the schema.

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?

Clearly states 'Pause a specific email in a classic automation workflow', specifying verb, resource, and context. Distinguishes from pausing the entire workflow, which is a sibling tool.

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?

Provides context by contrasting with pausing the entire workflow and mentions authentication, rate limits, and optional account usage. However, it does not explicitly state when not to use or list alternatives beyond the implicit contrast.

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