impreza_deploy_catalog_app

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

No annotations provided, so description carries full burden. It explains deployment involves target VPS, app name, optional version, domain, onion, and vars. However, it lacks details on idempotency, error behavior, or prerequisites like VPS readiness.

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?

Three sentences, front-loaded with main purpose, then guidance. Very concise but packed with information. Slightly dense but no filler.

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 deployment tool with 6 params and no output schema, it covers inputs (how to find app names and server IDs), alternative tool, and parameter usage examples. Missing success/error behavior but adequate for agent understanding.

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?

Schema coverage is 100%. Description adds examples for 'vars' (e.g., signups_allowed for Vaultwarden) and explains domain/onion relationship: 'Omit + set onion:true for onion-only.' This goes beyond schema descriptions.

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 states 'Install an app from the Impreza catalog... on a target VPS', clearly specifying verb, resource, and target. It distinguishes from the sibling 'impreza_deploy_custom' by noting that tool is for non-catalog apps.

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?

Explicitly directs to use 'impreza_list_apps' for app names and 'impreza_list_servers' for agent_id. Provides clear alternative: 'impreza_deploy_custom' for non-catalog apps.

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