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

Annotations already mark this as readOnlyHint=true, so the safety profile is covered. The description adds the resource scope and points to the deletion endpoint via api_request, which is useful context, but it does not disclose output shape, pagination, or filtering 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?

A single sentence with no fluff. The primary purpose is front-loaded, and the secondary deletion hint is appended efficiently after a semicolon, giving the agent maximum information per word.

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 simple read-only list with one optional parameter and no output schema, the description covers the core behavior and even points to the related DELETE endpoint. It is complete enough for basic invocation, though it could briefly mention that the returned schedules contain IDs used for deletion, and clarify the status filter.

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 0%, and the description does not mention the optional 'status' parameter at all. The enum values 'active', 'paused', and 'done' are self-explanatory, but the description fails to clarify that status can filter the listed schedules, so it under-compensates for the low schema 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 clearly states a specific verb and resource: 'List scheduled wake-ups'. It also distinguishes this read-only tool from deletion by referencing 'delete with api_request DELETE /v1/schedules/{id}', so an agent can tell what this tool does vs. what another tool handles.

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 tells the agent to use api_request for deleting schedules, which is clear when-not/alternative guidance. However, it does not address when to use this over other listing tools like list_jobs, making the guidance useful but slightly narrow.

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