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

Annotations already declare the write profile (readOnlyHint=false, idempotentHint=false, destructiveHint=false), so the bar is lower. The description adds real behavioral context beyond them: the all-optional-fields defaulting model and the specific failure mode '403 template_limit_reached' when the per-account cap is exceeded. It does not cover permissions/auth requirements or whether templates are mutable later.

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 final two sentences ('Fields for creating a site template. Only `name` is required; all others default to a new-template configuration.') duplicate the second and third sentences almost verbatim, wasting roughly a third of the text. The quota error, which is genuinely valuable, is buried mid-description rather than front-loaded.

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 12-parameter, deeply nested creation tool with no output schema, the description covers the essentials an agent needs (required field, defaults, quota error) and annotations carry the safety profile. It omits how a created template is used downstream and how it relates to create_site/update_site_template, leaving the agent with an adequate but thin picture.

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 coverage is 100%, so the schema already documents all 12 parameters and the required array already marks name as required. The description's note that only name is required and everything else defaults is largely a restatement of structured data, so baseline 3 applies.

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?

States a specific verb and resource ('Create a site template') and adds a useful definition of what a template is: a reusable bundle of site settings lacking url/paused/labels, which implicitly separates it from create_site. It stops short of naming a sibling explicitly, so it is clear but not maximally differentiated.

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?

Usage is only implied: 'Only name is required; every other field defaults to a new-template configuration' tells the agent the minimum viable call. There is no guidance on when to prefer this over create_site or update_site_template, and no prerequisites beyond the quota note.

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