Metis — Set Backup Schedule

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

No annotations are provided, so the description carries the full burden. It discloses that the tool only persists configuration and that older backups will be deleted based on keep_days when the scheduler runs. However, it does not mention authorization needed, error states, or reversibility of settings.

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 with a clear opening clause, a brief behavioral note, and a parameter list. Every sentence serves a purpose, and the most important information 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 the tool's purpose and all parameters well. However, it does not mention the presence of an output schema or what the tool returns (e.g., a confirmation or the schedule state). Slightly incomplete for a tool with an output schema, but otherwise comprehensive.

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 input schema has 0% description coverage, so the description must compensate. It adds meaningful explanations for all 4 parameters: enabled (on/off), time_utc (format hint 'HH:MM'), keep_days (retention policy), and destination (default path). This adds significant value beyond the schema's bare types 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 'Configure the nightly backup schedule' with specific verb and resource. It further explains that the schedule triggers backup_db() automatically and that this tool only persists the configuration, distinguishing itself from related tools like backup_db and get_backup_schedule.

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 implies usage context by stating the scheduler reads the schedule to trigger backup_db(), and that the tool only persists config. However, it does not explicitly state when to use this tool vs alternatives like backup_db for immediate backup or get_backup_schedule for viewing, nor does it provide when-not-to-use guidance.

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