update_client_template

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

With no annotations, the description must convey behavioral traits. It only says 'Update a client template (legacy).' It does not describe what happens on success/failure, idempotency, side effects, or any requirements like necessary permissions. This is insufficient for an update 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 very short, which is concise, but it sacrifices important information. It is front-loaded with the key action but lacks details. Ideally, it should be longer to include usage guidance or behavioral notes.

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 the complexity (3 required params, one nested object) and the existence of sibling tools for client templates (create, delete, get, list), the description is incomplete. It does not mention that this is an update operation on existing resources, nor does it explain the legacy status or any replacement. No output schema is provided.

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 description coverage is 100%, so the schema already documents parameters. The description adds no additional meaning or context beyond what is in the schema. For example, it does not explain what 'template_data' should contain or its format. 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 clearly states the action 'Update a client template' and marks it as 'legacy', which indicates its purpose. However, it does not differentiate it from other update tools like 'update_client' or 'update_client_scope', which could lead to confusion. The verb 'update' and resource 'client template' are specific enough.

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 provided on when to use this tool versus alternatives. The 'legacy' label hints that it might be deprecated or replaced, but no explicit instructions or references to a newer version are given. There is no discussion of prerequisites or context.

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