cloud_enable_server_backup

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

No annotations provided; description only mentions cost. Does not disclose side effects, like impact on server performance, backup schedules, or how existing backups are handled.

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?

Extremely concise single sentence that front-loads the action. No unnecessary 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?

Despite low complexity and existence of an output schema, the description omits key details like success response, failure conditions, or idempotency. Insufficient for reliable agent use.

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 'server_id' is documented only in the schema; description adds no extra meaning (e.g., format, range, or how to obtain it). With 0% schema coverage, the description fails to compensate.

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 (enable automatic backups) and the target resource (a server). It also notes additional cost, distinguishing it from sibling cloud_disable_server_backup.

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 on when to enable backups vs. alternatives like cloud_disable_server_backup. No prerequisites or context provided, such as requirement that the server already exists or whether backups are already enabled.

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