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

Annotations already indicate readOnlyHint=false, destructiveHint=false, and idempotentHint=false. The description adds 'Effect: workspace-change' and permission requirement, which is useful. However, it doesn't disclose details about what happens on creation (e.g., whether it activates immediately, validation behavior) beyond the schema. No contradiction with annotations.

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 concise (three sentences) and front-loaded with the primary action. It includes essential operational details (effect, retry, permission, API reference) without fluff. Slightly dense but efficient.

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 the complex nested schema (AutomationDefinition with many step types) and output schema present, the description is adequate but not complete. It doesn't mention validation rules, activation behavior, or how to construct the definition. The API reference link helps, but the description could provide more guidance on the automation definition structure.

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 description coverage is 100% (both body and idempotency_key have descriptions). The description adds the idempotency_key retry semantics, but the body parameter is already described as 'exact JSON request body defined by the Mailrith public API contract.' The description doesn't add much beyond the schema, so baseline 3 is appropriate.

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 tool creates an automation in the authenticated workspace, which is a specific verb+resource. It distinguishes from siblings like automations_update and automations_list, though it doesn't explicitly contrast with them.

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 description mentions retry with idempotency_key and permission requirement, but does not provide explicit guidance on when to use this tool versus alternatives like automations_update or sequences_create. The context is clear but no exclusions or alternative recommendations are given.

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