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

Annotations supply only readOnlyHint=false, so the description carries most of the burden and does it well: it discloses the default schedule-shifting side effect, the opt-out via shiftSchedule, and the confirm-gated preview-then-execute flow. What is not covered is behavior when the enrollment is not paused, or whether prior occurrences are also shifted.

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 sentences, front-loaded with the action, followed by the default behavior and the gating rule. The nested parentheticals are slightly dense but each clause carries distinct information, so nothing is wasted.

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 three-parameter mutation with no output schema and minimal annotations, the description covers the essentials: what it mutates, the default side effect, how to override it, and the two-step confirm flow. Edge cases around non-paused enrollments and downstream occurrence regeneration are the only notable omissions.

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 only 33% (only `confirm` is documented in the schema), yet the description explains the semantics of `shiftSchedule` precisely — default true shifts remaining days forward, false preserves original dates. The `id` parameter is left implicit, but its meaning as the enrollment identifier is unambiguous from context.

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 opens with a specific verb+resource ("Resume a paused program"), which cleanly separates it from pause_program_enrollment, cancel_program_enrollment, and resume_organization_subscription in the sibling list. It stops short of naming those siblings explicitly, so the differentiation is inferred rather than stated.

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?

Usage is implied by the precondition "paused program", which tells the agent the enrollment must already be paused. There is no explicit when-not guidance or pointer to adjacent tools such as shift_program_enrollment_start or edit_program_enrollment for alternative rescheduling needs.

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