Create Backup

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

No annotations are present, so the description carries the full burden. It only says 'Create a local JSON backup' without explaining if it overwrites existing backups, where the backup is stored, or what the return value is. This is insufficient for a write operation.

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 a single sentence, which is concise but lacks essential details. It achieves brevity at the cost of completeness, making it marginally acceptable.

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 parameter, no output schema), the description should explain the outcome (e.g., file path, success indication) and what 'configuration endpoints' encompasses. It fails to provide a complete picture, leaving the agent with ambiguities.

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 single parameter 'app' is an enum of Servarr apps, but the description provides no explanation of its meaning or how to use it. With 0% schema coverage, the agent is left to guess that it selects the app to back up.

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 ('Create'), resource ('local JSON backup'), and scope ('Servarr configuration endpoints'). It effectively distinguishes from sibling tools like list_backups and restore_backup, but could be more specific about which endpoints are included.

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 is provided on when to use this tool versus alternatives such as restore_backup or other backup-related operations. There is no mention of prerequisites, intended use cases, or 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.