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

Annotations already declare readOnlyHint=false, destructiveHint=false, openWorldHint=false, so the mutation profile is covered. The description adds genuinely useful non-obvious behavior: idempotency (an existing draft is returned rather than a new one created) and the draft's editability/publiability. No auth or rate-limit context, but the key behavioral trait is disclosed.

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 core purpose and idempotency constraint are front-loaded in the first two sentences, and the numbered workflow is scannable. The workflow list is somewhat long but each step carries distinct routing value, so little is wasted.

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?

With no output schema, the description compensates by telling the agent that a design ID is returned and consumed by start-editing-transaction. Annotations cover the safety profile, so the combination is nearly complete; only the relationship to create-design-from-brand-template is unaddressed.

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% and both parameters are documented in the schema (brand_template_id even points to search-brand-templates). The description adds no additional semantics for brand_template_id or user_intent, so the 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 (creates an editable draft design from a brand template) and adds the key behavioral distinction that the draft can be edited and published back. It does not explicitly contrast itself with the similarly-named sibling create-design-from-brand-template, so sibling differentiation is left to inference.

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?

Explicitly states when to use it ('to get a design that can be edited and later published back') and provides a full ordered workflow naming the alternative tools (start-editing-transaction, perform-editing-operations, commit-editing-transaction, publish-brand-template) for the Autofill/tagging case. Nothing is left to guesswork.

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