Create Bundle Template

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

The description discloses that it copies local tags and optionally entries, but does not explain the 'confirm' parameter's behavior, potential side effects, or what creation entails. Annotations provide no safety signals (all false), so the description carries the full burden and falls short.

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 clear sentence that front-loads the action. It contains no filler and each word adds information.

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 mutation tool with no output schema and no positive annotation signals, the description does not explain the confirmation flow, return value, or any side effects. It covers the core purpose but leaves significant operational context unresolved.

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%, so the description must compensate. It explains include_entries via 'optionally entries' and alludes to bundle_id and name, but leaves 'confirm' and 'description' unexplained. The confirm parameter's semantics are non-obvious and underexplained.

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 uses a specific verb ('Create') and resource ('custom template'), and specifies the source ('from a bundle') and key behavior ('copying local tags and optionally entries'). This clearly distinguishes it from sibling tools like bundled_apply_template and bundled_create_bundle.

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 description implies when to use the tool (when creating a template from a bundle) but provides no explicit guidance on when not to use it or how it compares to sibling tools. It lacks any mention of alternatives or prerequisites beyond the required bundle_id.

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