ubuntu_website_deployment

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions 'deploy' and 'create backups' but doesn't specify critical details like whether this is a destructive operation (e.g., overwriting files), permission requirements, error handling, or backup retention. This leaves significant gaps for safe usage.

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, efficient sentence that front-loads the core functionality ('Deploy website files and create backups on Ubuntu') with zero wasted words. It's appropriately sized for the tool's complexity and easy to parse.

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?

For a tool with 7 parameters, no annotations, and no output schema, the description is incomplete. It doesn't address behavioral aspects like safety (e.g., whether deployment overwrites existing files), error conditions, or what the tool returns. Given the complexity and lack of structured data, more context is needed for reliable 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 schema has 100% description coverage, so parameters are well-documented in the schema itself. The description adds minimal value beyond implying the tool handles website files and backups, but it doesn't provide additional context like file format expectations or backup naming conventions. Baseline 3 is appropriate given the schema does the heavy lifting.

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's purpose with specific verbs ('deploy website files' and 'create backups') and resource ('on Ubuntu'), making it easy to understand what the tool does. However, it doesn't explicitly differentiate from sibling tools like 'ssh_upload_file' or 'ubuntu_nginx_control', which might handle similar operations.

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 provides no guidance on when to use this tool versus alternatives like 'ssh_upload_file' for file transfers or 'ubuntu_nginx_control' for web server management. It mentions the action parameter includes 'deploy, backup, restore' but doesn't explain when each is appropriate or any prerequisites.

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