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

Annotations already declare non-read-only, non-destructive, non-idempotent, open-world. The description adds substantive behavior beyond that: a monitor-scope auth requirement, preservation of the original expiry and budget, and the important side-effect nuance that an already queued operation is not cancelled. That is exactly the kind of consequence detail annotations cannot convey.

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?

Four tight sentences, front-loaded with the action and scope before the constraints. Every clause earns its place — scope requirement, preservation semantics, queued-op caveat, and the complement tool.

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 single-parameter mutation with annotations covering the safety profile and no output schema, the description covers auth, reversibility via resume_monitor, and partial-effect behavior. It says nothing about the response or whether repeated pauses are rejected, which is minor but a gap.

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?

There is one parameter ('id') and schema description coverage is 100%, with the schema stating 'Owned monitor_id to pause.' The description adds no syntax or format detail beyond what the schema already documents, so the baseline of 3 applies.

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+resource ('Pause future scheduled runs for an owned monitor') with clear scope ('owned', 'future scheduled runs'). It is immediately distinguishable from the sibling resume_monitor, which is also named.

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?

Names the complementary alternative and its effect ('Use resume_monitor to restart within the same bounds') and states the scope prerequisite, giving an agent clear routing. It stops short of an explicit when-not-to-use condition, so it is clear context rather than full when/when-not guidance.

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