create_template

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

No annotations are provided, so the description must fully disclose behavior. It states the creation action and the template's purpose, but does not specify persistence, idempotency, authorization requirements, or what happens on duplicate names. The description is adequate but lacks depth 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 three sentences long, front-loaded with the verb and resource, and every sentence adds value. No redundant or vague phrasing.

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?

Given the tool's complexity (nested object, no output schema), the description covers the main purpose and use case. It lacks details on return value, error handling, and whether settings are optional, but it provides sufficient context for an agent to understand the tool's role among siblings.

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?

With 0% schema description coverage, the description compensates partially by explaining that settings include default destinations, UTM parameters, targeting rules, and attribution windows. However, it does not mention the required 'name' parameter, nor 'description', 'isDefault', or 'expiresAfterDays'. Nested fields are hinted but not fully detailed.

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 clearly states the verb 'Create' and the resource 'link template', and explains what templates do (default destinations, UTM parameters, targeting rules, attribution windows). It distinguishes from siblings like create_link and set_default_template by focusing on creating a reusable template, not a link or setting defaults.

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 mentions that templates are 'useful for ensuring consistency across campaigns', implying when to use, but does not provide explicit when-not-to-use conditions or alternative tools. No exclusions or prerequisites are stated.

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