pause_schedule

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

No annotations provided, but description discloses temporary behavior, preservation of config, and ability to resume. Does not mention potential side effects like dropped notifications or 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?

Three concise, informative sentences. Front-loaded with purpose, then details, then source of ID. No wasted words.

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?

Given the simplicity of the tool (one param, with output schema), description covers the essential behavior. Could mention idempotency or error cases, but not critical.

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?

Only one parameter (schedule_id), fully described in schema. Description adds value by specifying where to obtain the ID (from schedule_cron_notification).

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 'Pause a scheduled notification' clearly, with verb and resource. Mentions temporary stop and resumption, distinguishing from deletion. However, does not explicitly contrast with delete_schedule or other siblings.

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?

Implies usage after creating a schedule to temporarily stop it, and notes resumability. No explicit 'when not to use' or comparison with alternatives like delete_schedule.

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