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

Annotations already declare destructive=true, idempotent=true, readOnly=false, so the safety profile is covered. The description adds genuinely new behavioral context beyond that: it does not run the recipe, and in-flight work may still complete — telling the agent this is a soft stop rather than a cancellation. It omits auth/permission requirements, but the added semantics are substantive.

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 short sentences, front-loaded with the core action and followed by two clarifying constraints. No filler, no repetition of the name.

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?

An output schema exists and annotations carry the safety profile, so return values and risk are adequately covered. The remaining gap is routing and parameter meaning for a tool that sits among resume_*, archive_*, and get/list automation siblings. Minimum viable, but not complete.

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 0% and the description documents none of the four parameters. brandId, automationId, revision, and idempotencyKey carry format/pattern constraints in the schema but no meaning is added anywhere — notably 'revision' (a concurrency token) and 'idempotencyKey' are left for the agent to guess. The description fails to compensate for the coverage gap.

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?

States a specific verb (pause) and resource (a saved automation) and narrows scope to 'future runs', which is precise. It does not, however, name or contrast itself with the numerous sibling tools (resume_* automations, archive_automation), so the agent must infer the boundary. Clear, but no sibling differentiation.

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 on when to pause versus archiving, resuming, or deleting an automation, and no prerequisites are stated. The description explains the effect of pausing but never frames the decision context. Comparable to the MID calibration example, which also scored 2 for absent when-to-use guidance.

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