Update Template Metadata

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

The description explains that expireAt can schedule or trigger immediate deletion, which contradicts the annotation destructiveHint: false. This inconsistency reduces transparency, as the annotation suggests no destruction, yet the description indicates destructiveness.

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 concise: two sentences that front-load the key information (updateable fields) followed by specific usage notes for deployedAt and expireAt. No redundant or irrelevant text.

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 description covers the main functionality but lacks information about expected output or success/error responses. Given no output schema, the agent might need more context on what happens after an update (e.g., confirmation, errors).

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?

With 100% schema coverage, the description adds value by explaining that deployedAt activates a specific version for rendering and that expireAt can delete immediately. It also clarifies that templateId can be a template ID or version ID, affecting whether updates apply to all versions or a specific one.

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 verb 'Update' and the resource 'metadata of a stored template', listing specific fields (name, comment, category, tags, deployment timestamp, or expiration). It distinguishes from sibling tools like delete_template and upload_template by focusing on metadata updates.

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 does not explicitly state when to use this tool versus alternatives, nor does it mention when not to use it. Usage context is implied through sibling tool names, but lacking direct guidance.

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