server_provision

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

Discloses key traits: creates a billable resource (aligns with destructiveHint=true), estimated initialization time (3-5 minutes), and environment variable requirements. Adds significant context beyond annotations, which are already present.

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?

Five concise sentences with no redundancy. Front-loaded main purpose, then specifics. Every sentence adds critical information (mode, tokens, warning, timing).

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?

Covers all essential aspects: what it does, parameters (schema already detailed), preconditions, side effects, and behavior. With output schema present, description does not need to explain return values.

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%, so baseline is 3. Description adds value by explaining the 'bare' mode behavior and linking mode to Coolify/Dokploy, enhancing understanding 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?

Description clearly states 'Provision a new server on a cloud provider' with a specific verb and resource. Distinguishes from sibling tools (e.g., server_audit, server_backup) by focusing on creation rather than management or 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?

Describes when to use (provisioning a server), prerequisites (provider API tokens), and conditions to avoid (KASTELL_SAFE_MODE=true). Does not explicitly compare to alternative siblings, but the unique purpose is implied.

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