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

Annotations only indicate that the tool is not read-only and not destructive. The description adds meaningful behavioral context: paused schedules stop generating invoices, due periods continue accumulating, and resuming later back-bills them. This goes beyond structured fields, though it does not cover repeated-pause or error behavior.

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 dense, purposeful sentences. The first front-loads the core action and non-destructive nature; the second adds the critical resumption-side-effect and routes to the correct sibling tool. No filler or 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?

For a single-parameter mutation tool, the description covers the central side effects and the alternative tool. The main gap is that it never explicitly maps the 'id' parameter to the schedule entity, but the low complexity and strong sibling differentiation keep this from being a major omission.

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 coverage is 0% and the sole required parameter 'id' has no schema description. The description never mentions that id identifies the schedule to pause. With low schema coverage, the description should compensate by explaining the parameter, but it does not.

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 uses a specific verb and resource: 'Stop one schedule generating invoices without deleting it.' It clearly differentiates the tool from schedule_delete (no deletion) and from generation tools like invoice_generate_due and forecast, which will skip the paused schedule.

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 explicitly states when to use schedule_pause versus schedule_skip: pause stops invoice generation indefinitely while periods continue falling due; schedule_skip is for dropping a single occurrence. It also clarifies that generation and forecast tools will skip the paused schedule, giving an agent a clear decision path.

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