deploy_template

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only says 'Deploy' without explaining side effects, whether it creates a project or app, required permissions, idempotency, or failure modes. This is a significant transparency gap for a mutation-like 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 with no wasted words and front-loads the main action. It is concise, though it sacrifices useful detail that could have been added without significant bloat.

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 deploy tool with no output schema, no annotations, and a nested schema object, this description leaves the agent without knowledge of what the deployment produces, what preconditions exist, or what the template schema should contain. Sibling tool names alone are insufficient to convey complete usage context.

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 input schema only documents 'schema' as 'Template schema object' and leaves 'projectName' undocumented, giving 50% coverage. The description adds the phrase 'one-click template' but does not clarify how projectName and schema are used or what structure the template schema should have.

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 uses a specific verb ('Deploy') and identifies the resource as an EasyPanel one-click template, which matches the tool name and broadly distinguishes it from deploy_app and deploy_compose. It does not explicitly contrast with sibling deployment tools, but the resource type is clear.

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 template reference implies this tool is for deploying from one-click templates, but there is no explicit guidance about when to use it instead of deploy_app, deploy_compose, or create_app. Usage context is implied rather than stated, and no exclusions or alternatives are named.

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