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

With readOnlyHint, idempotentHint, and destructiveHint already present, the annotations cover the safety profile. The description adds a meaningful behavioral requirement — authentication via the login tool — which the agent must know before invoking.

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, no filler, with the primary action and resource front-loaded. The prerequisite is stated immediately after the main purpose, making the description efficient to parse.

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 one-parameter, read-only, non-destructive list operation, the description is essentially complete: what it lists, whose data it shows, and what credential is required. No output schema exists, but 'List ... schedules' sufficiently implies the response form for this simple tool.

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?

The schema already documents the token parameter with 100% coverage, so the description does not need to re-explain it. The description's 'Requires a login token' line reinforces the dependency but adds little beyond the schema.

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 states a specific verb ('List') and resource ('your saved Rhylthyme schedules'), so the core operation is immediately clear. It does not name a sibling tool or an explicit differentiation path, but the 'your saved' scope makes it distinguishable from list_public_runs and list_runs in practice.

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 gives a clear precondition: the user needs a login token from the login tool. It does not explicitly state when to prefer this tool over siblings such as list_public_runs or load_program, leaving some inference to the agent.

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