Create Backup

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

The description claims to 'Schedule a new backup', suggesting each call creates a new backup. This contradicts the idempotentHint: true annotation, which implies repeated calls have the same effect. Additionally, the description adds 'runs in the background' but doesn't clarify idempotency behavior.

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 extremely concise with two short sentences, no filler, and all information is front-loaded. Every sentence contributes value.

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 no output schema and no parameters, the description should be self-contained. It fails to clarify critical behavior like idempotency, what happens if a backup is already in progress, or scheduling details. The contradiction further reduces completeness.

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?

There are no parameters, so schema coverage is 100%. The description adds no parameter information, which is acceptable as there's nothing to add. Baseline for zero parameters is 4.

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 action ('Schedule a new backup') and the resource ('Homey configuration'). It distinguishes from sibling 'get_backup_status' by indicating creation vs monitoring.

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 for creating backups but provides no guidance on when to use this tool versus alternatives. No explicit when-not or comparison to get_backup_status is given.

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