schedule_notification

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

Annotations indicate a write operation but not destructive or idempotent. The description adds the '[Write]' tag, confirming it's a write, but does not disclose other behaviors like whether it overwrites existing schedules, validates schedule formats, or requires specific permissions.

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?

Very concise, one sentence. No unnecessary information, but it could be slightly more structured (e.g., separating purpose from usage).

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?

Minimal description adequate for a simple tool with few parameters and annotations. However, it lacks information about return values (e.g., success/failure) and edge cases like invalid notification_id, which would be helpful.

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 descriptions cover all three parameters (notification_id, schedule, active) with clear meanings. The tool description does not add additional context beyond the schema, so it meets the baseline for 100% 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 it schedules a notification for future delivery, using specific verb 'Schedule' and resource 'notification'. It distinguishes from sibling tools like create_notification and update_notification, though it could be more explicit that it operates on an existing notification rule.

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?

No guidance on when to use this tool versus alternatives such as create_notification or update_notification. The description lacks context about prerequisites or conditions for scheduling.

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