update_native_template

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

With no annotations, the description carries the burden of behavioral disclosure. It usefully reveals that variables use an add/remove format, which is non-obvious from the schema alone. However, it does not disclose whether name/raw_html are partial updates, whether id is required, or what the response looks like.

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 two short sentences with no wasted words. The first sentence clearly states the action and target, and the second adds the key variable-update behavior.

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 schema covers parameter details well, but there are no annotations and no output schema. The description leaves out return value, error behavior, and whether fields are partially updated. The add/remove hint is helpful, but the overall context is not fully complete for a nested update tool.

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%, providing a solid baseline. The description adds value beyond the schema by clarifying that the variables parameter uses add/remove arrays for updates, which is essential semantic context not fully captured by the property 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?

The description explicitly states 'Update an existing native template', using a specific verb and resource. This clearly distinguishes it from sibling tools like create_native_template, delete_native_template, and get_native_template.

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 'Update an existing' implies this tool is for modifying existing templates rather than creating new ones, but there is no explicit when-to-use guidance, prerequisites, or mention of alternatives. It does provide a meaningful usage hint about the add/remove format for variables, but not for tool selection.

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