template_create

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

With no annotations provided, the description carries the full burden. It discloses key behaviors: the precedence of 'templates' over single fields, support for one or many records, and the return value. It does not mention authentication, idempotency, or side effects beyond creation, but the most important operational details are present.

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?

Two sentences that are front-loaded with the tool's purpose, followed by concise instructions on single/bulk usage, precedence, and return value. Every sentence earns its place with no wasted words.

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 9 parameters and rich schema, the description is adequately complete. It covers both creation modes, precedence, and return value. The schema handles field-level details, and while an output schema is absent, the mention of returning created record(s) helps.

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?

The input schema already provides 100% coverage with detailed parameter descriptions, so the description adds limited value here. It clarifies the relationship between top-level fields and the 'templates' array, but the schema itself documents required fields and defaults. 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?

Clearly states 'Create one or more content templates for the brand' with a specific verb and resource. It distinguishes from sibling tools like template_list, template_update, and template_delete by emphasizing the create action and the added bulk-creation capability.

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?

Provides clear context for when to use the tool, including the choice between single and bulk creation and an explicit precedence rule. It does not explicitly name alternative tools for update/delete or state when not to use this tool, so it falls just short of a 5.

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