template_customize

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

With no annotations provided, the description must carry the full burden. 'Customize' implies a mutation, but the description does not disclose whether changes are persistent, reversible, require permissions, or how 'overrides' are applied. This is a significant transparency gap.

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 single sentence is efficient and front-loaded, but it largely restates the tool name. 'With specific overrides' adds only marginal value since the schema already documents the overrides parameter, so the sentence does not fully earn its place.

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?

The tool has four parameters, including a nested overrides object, and an output schema, yet the description is only one sentence. It does not explain usage context, differences from sibling tools, or any behavioral caveats, making it inadequate for confident tool selection.

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 has 100% description coverage for all parameters, so the baseline is 3. The description's phrase 'specific overrides' adds minimal meaning beyond the schema's already-clear 'Dictionary of values to override in the template'.

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 the specific verb 'Customize' with the resource 'template', and 'with specific overrides' clarifies the scope. However, it does not distinguish this tool from sibling template-modification tools like cases_update_template, so it falls short of a 5.

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?

No guidance is given on when to use this tool versus alternatives such as template_list, template_get, or cases_update_template. There is no mention of exclusions, prerequisites, or fallback scenarios.

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