set_backup_schedule

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

No annotations are provided, so the description carries full burden. It states the tool 'only persists the configuration' and does not trigger backup, which is helpful. However, it lacks details on side effects, permissions, parameter validation, or confirmation messages, leaving gaps in behavioral clarity.

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?

The description is concise and well-structured: a single introductory sentence establishing purpose, followed by a clear bullet list for parameters. No unnecessary information, and the purpose is 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?

The description covers purpose and parameters adequately. Since an output schema exists, return values are not required, but the description omits potential error conditions or prerequisites (e.g., scheduler phase). Nonetheless, for a simple configuration tool, it is reasonably complete.

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%, so the description must compensate. It does so effectively with a bullet list explaining each parameter (enabled, time_utc format, keep_days retention, destination default), adding meaningful context beyond the schema's titles and defaults.

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 configures a nightly backup schedule, using specific verb 'configure' and resource 'nightly backup schedule'. It distinguishes from siblings like get_backup_schedule (read) and backup_db (execute backup), leaving no ambiguity about its purpose.

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 explains that the schedule is read by the scheduler to trigger backup_db() automatically and that the tool only persists configuration, implying it is for setting up schedules rather than immediate execution. However, it does not explicitly state when to use this tool versus alternatives like get_backup_schedule or backup_db, or specify when not to use it.

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