Update template

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

Annotations indicate idempotentHint: true, destructiveHint: false, and readOnlyHint: false. The description adds no behavioral context beyond what annotations already provide, such as whether partial updates are supported or what happens to unspecified fields. It does not contradict annotations.

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, direct sentence with no extraneous information. Every word contributes to stating the tool's purpose efficiently.

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?

Without an output schema, the description should mention return value or behavior. It does not say whether the updated template is returned or only a success indicator. Given the tool's simplicity (5 params, no nested objects) and comprehensive sibling tools, additional context about usage or response would improve completeness.

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 descriptions for each parameter. The description adds value by clarifying that the template is a Docker Compose template, implying the 'content' parameter expects YAML. However, it does not explicitly clarify that all fields except templateId are optional for partial updates, though the schema's required list implies it.

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 a Docker Compose template', specifying the verb 'Update' and the resource 'Docker Compose template'. Among sibling tools, it is distinct from create, delete, get, and update_variables, making its purpose unambiguous.

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 provides no guidance on when to use this tool versus alternatives. For example, it does not mention that for updating only variables, 'arcane_template_update_variables' should be used, nor does it specify prerequisites or context for use.

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