save_template

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

With no annotations provided, the description carries the full burden of disclosing behavior. It states 'overwrite', which implies idempotent replacement, but it does not mention any side effects, authentication requirements, potential data loss, or response behavior. This is minimal disclosure for a mutation tool.

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 a single, concise sentence with no filler. It is appropriately sized for a simple save operation. However, it could be slightly more informative without being verbose, hence a 4 rather than a 5.

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 straightforward create/overwrite operation, the description is minimally sufficient. The presence of an output schema means return values are covered elsewhere. However, given no annotations and no mention of overwrite semantics (e.g., whether it replaces entirely), the description lacks some context that would help an agent understand edge cases. Overall, it is adequate but not complete.

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%, with each parameter (body, name, subject) having its own description. The tool description adds no extra semantic meaning beyond the schema, which is acceptable given the high coverage. Baseline 3 is appropriate.

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 states a clear action ('Create or overwrite') and resource ('a template'), making the purpose understandable. It does not explicitly distinguish from sibling tools like get_template or render_template, but the verb clearly implies a save operation, which is distinct from reading, rendering, or deleting. Slight deduction for not naming any sibling to avoid confusion.

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?

No guidance is given on when to use this tool versus alternatives. It does not mention that this is for creating new templates or modifying existing ones, nor does it reference any sibling tools. The agent must infer usage from the name and brief description, which is insufficient for a tool with many related operations.

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