Save a template

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

Beyond the annotations the description discloses two real behaviors: templates are stored as JSON files in a templates folder, and `extends` inherits from another template while tags and hashtags are merged rather than replaced. It says nothing about validation failures, what happens to omitted fields on replace, or how deeply inheritance is resolved.

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 short sentences, front-loaded with the core action, with no filler. The final clause 'tags and hashtags combine' is telegraphic but still intelligible.

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?

For a 16-parameter mutation tool with no output schema and no annotation coverage of field semantics, the description is far too thin: most fields an agent must supply are undefined, and replace-vs-merge behavior is only stated for tags and hashtags, not for the rest of the payload.

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 0% across 16 parameters, so the description must carry the load, but it only explains title_format ('{title}'), extends, tags and hashtags. Twelve parameters — including the license enum, embeddable, made_for_kids, category_id, playlists, and the description header/footer fields — get no meaning at all.

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?

States a specific verb and resource ('Create or replace a metadata template') plus where it is persisted (JSON in the templates folder). It is clearly distinguishable from delete_template and list_templates, though it never names those siblings explicitly.

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 phrase 'Create or replace' implies the tool is the upsert path for templates and that an existing template with the same name is overwritten. There is no explicit guidance on when to save versus delete, or on prerequisites such as an existing name collision check.

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