list_scheduled_notifications

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

No annotations are provided, so the description carries the burden. It accurately describes the tool's behavior: returns all recurring schedules, optionally filtered by topic, and explicitly excludes one-off notifications. This adds value beyond the schema without contradictions.

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 concise sentences: first states purpose, second defines scope, third clarifies exclusion. No redundancy, every sentence adds value. Well-structured and front-loaded.

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?

With one optional parameter and an output schema, the description is complete. It sufficiently explains the tool's function and filtering capability, leaving no critical gaps for an agent to understand usage.

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 100% with one parameter fully described. The description only restates that filtering is optional, adding minimal extra meaning. Baseline 3 is appropriate as the schema already covers details.

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 the tool lists scheduled recurring notifications, differentiating from one-off notifications. The verb 'list' and resource 'recurring cron notification schedules' are specific, and the note about exclusions distinguishes it from sibling tools like schedule_notification.

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 clarifies the tool returns recurring schedules, not one-off notifications, and mentions optional filtering. It implicitly guides when to use this tool versus schedule_notification, but lacks explicit exclusion guidance for other siblings like delete_schedule or pause_schedule.

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