update_template

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

No annotations are provided, so the description carries full burden. It states 'Update an existing template' and notes the return is an empty dict on success. It does not disclose side effects, authentication needs, or whether omitted fields remain unchanged. For a mutation tool, more behavioral context would be beneficial.

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 lengthy but well-structured with parameter lists and a notable nested explanation for task_params. It is front-loaded with the purpose, then a clear args list. Some redundancy in listing optional status could be trimmed, but it remains readable.

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?

Given 21 parameters, the description covers all of them, explains the return value, and provides enough context for an agent to understand the tool's use. No output schema is present but is not needed as return type is specified.

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?

Despite 0% schema description coverage, the description compensates thoroughly by listing all 21 parameters with explanations. It marks optional parameters and provides detailed sub-parameters for task_params, especially for Ansible templates. This adds significant meaning beyond the schema.

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 'Update an existing template.' This is a specific verb and resource, distinguishing it from create_template, delete_template, and get_template among siblings.

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 implies usage for updating existing templates via the verb 'Update' and the required template_id parameter. However, it lacks explicit when-to-use or when-not-to-use guidance or references to alternative tools.

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