template_deploy

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

No annotations provided, so description carries burden. It labels the tool as '[WORKFLOW]' and mentions prerequisites/alternatives, but does not disclose side effects, authorization needs, rate limits, or what gets created/destroyed. Lacks behavioral depth expected for a workflow tool.

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?

Well-structured with bullet points and clear sections, front-loading the main purpose. Slightly verbose due to multiple sections, but every sentence adds value and the structure aids readability.

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?

Provides good contextual clues (prerequisites, alternatives, next steps) but omits details about the return value (e.g., deployment ID or status) and does not explain parameter relationships. Given no output schema, this is a notable gap.

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% with descriptive parameter names and descriptions in the schema. The description adds no extra meaning beyond the workflow context, so baseline 3 is appropriate.

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 'Deploy a new service from a template' (specific verb+resource) and distinguishes from siblings like service_create_from_repo and database_deploy via explicit 'Not for' and 'Alternatives' sections.

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?

Provides explicit 'Best for' and 'Not for' sections, prerequisites (template_list), alternatives (service_create_from_repo, etc.), next steps, and related tools, giving comprehensive when-to-use and when-not-to-use guidance.

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