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

The description adds concrete behavioral details beyond annotations: future scheduling stops, nextRunAt becomes null, and active runs/pending deliveries are unaffected. It also reiterates idempotency (already in annotations). It does not mention permissions or rate limits, but for a simple pause operation, this is quite transparent.

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?

Two concise sentences, front-loaded with the core action and key behavioral effects. No filler or redundancy; every sentence earns its place.

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?

For a mutation tool with no output schema and annotations covering safety, the description is nearly complete: it explains what the tool does, what happens to scheduling, and what is not affected. It could mention authentication needs or edge cases, but overall it provides sufficient context for an agent to invoke it correctly.

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 high (83%), so the schema already documents most parameters. The description does not add any parameter-specific meaning, and the one parameter lacking a schema description (automation_id) is not clarified in the description. Baseline 3 is appropriate given the high 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?

The description states a specific verb (Pause) and resource (automation), and clarifies that active runs and pending deliveries are not canceled, which distinguishes it from delete_automation. However, it does not explicitly name sibling tools like resume_automation or delete_automation, so the differentiation is implicit rather than explicit.

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 implies when to use this tool (when you want to stop future scheduling but keep active runs) but does not explicitly state when to use it versus alternatives such as delete_automation or resume_automation. No exclusions or explicit comparisons are given.

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