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

Annotations already declare readOnlyHint=false and destructiveHint=true, so the mutation profile is known; the description adds the non-obvious recovery path ('The user can resume it from the Lection dashboard') and the confirmation requirement, which are real behavioral context the annotations do not carry. It does not say what happens when the schedule is already paused or the id is invalid.

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, the core action front-loaded, followed by the recovery path and the safety instruction; every sentence carries distinct information with no padding.

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, no-output-schema tool with rich annotations, the description covers purpose, reversibility, and the confirmation requirement. Only edge-case behavior (already-paused schedule, schedule ownership validation, error mode) is left implicit.

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 100% and the schema field already explains the UUID and points to list_my_schedules as the source, so the description adds no parameter meaning. Baseline 3 is appropriate for a single fully-documented parameter.

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 schedule belonging to the user) plus the resulting effect ('so it stops running'), which lets an agent distinguish it from list_my_schedules and schedule_extraction without opening the schema.

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?

Gives a clear operating condition (pause to stop a running schedule) and an explicit procedural prerequisite ('Confirm with the user first'), but names no alternative tool or exclusion cases because none exist among the siblings.

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