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

Annotations already declare readOnlyHint=false, destructiveHint=false, and openWorldHint=false, so the mutation/safety profile is covered. The description adds the persistence-for-reuse relationship and the designId linkage, but says nothing about required permissions, plan limits (e.g. hideLogo not on Free), or what happens on name collisions.

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 short sentences, zero filler, and the core action is front-loaded before the designId linkage. Nothing to trim.

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?

No output schema exists, so the description carries the return-value burden; it only indirectly implies a designId is produced. For a tool with a large nested spec object and no return documentation, the description is adequate but leaves key gaps (return shape, error/limit behavior).

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 50%: the spec object is documented exhaustively in the schema, but the required 'name' parameter has no description anywhere. The description only points out that spec fields match a preview design, adding a useful cross-reference but not compensating for the undocumented name semantics (uniqueness, reuse constraints).

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 (save a QR design for reuse) and ties it to how QR codes consume it via designId, which separates it from designs_update and qrs_create. Sibling differentiation is implicit rather than explicit, but an agent can identify the tool's role.

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 phrase 'for reuse' plus the designId reference implies you create a design once and attach it to QR codes, giving usable context. However, there is no explicit when-to-use versus designs_update/templates_create, and no prerequisite or exclusion guidance.

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