update_template

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

Discloses partial update behavior, authentication requirements, rate limit (max 10 concurrent requests), respect for read-only/dry-run modes, and 404 error for invalid template_id. All relevant behavioral traits are covered.

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?

Well-structured with clear sections and bullet points. Front-loaded with main action. Every sentence adds value without redundancy.

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?

Output schema exists, yet description still summarizes return JSON fields. With no annotations, description covers authentication, errors, and sibling differentiation. Complete for the tool's 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?

Input schema has 0% description coverage, but description adds meaning: template_id as numeric string from list_templates, name as new display name, html as content replacement. Fully compensates for schema's lack of descriptions.

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?

Clearly states 'Update an existing template's name or HTML content' and distinguishes from gallery/base templates, which only user-created templates can be updated. Also references the sibling tool create_template for creating new templates.

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?

Explicitly states when to use (update user-created templates) and when not (gallery/base templates), suggests using create_template instead. Also mentions authentication via API key, rate limit, and dry-run mode support.

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