origin_update_template_metadata

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

With no annotations, the description covers partial update behavior, no file modification, and a specific failure return (updated: false, not_found). Adds value beyond the schema.

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?

Three concise sentences front-load the purpose and behavior, with no extraneous information. Every sentence adds value.

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?

Covers update behavior, failure case, and relationship to sibling tools. Lacks explicit success return details, but output schema is present, so not critical. Adequate for the complexity.

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 0%, but the description mentions example fields (tags, description, matching hints) and partial update behavior. However, it does not detail all six parameters (e.g., plot_types, roles, n_columns), leaving gaps.

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 it edits a saved template's searchable metadata, using the verb 'Edit' and specifying the resource. It distinguishes from siblings like 'rename_template' and 'delete_template' by noting no file modification.

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?

It explicitly advises using this tool to fix tags, description, or matching hints without re-saving, and implies not for renaming or deletion. Omitted fields are left untouched, providing clear guidance.

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