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

Annotations already declare readOnlyHint=true, so the safety profile is covered; the description adds useful substance by disclosing what each returned item represents (reusable style attributes: colors, shapes, center logo/emblem). It does not discuss ordering, whether built-in templates appear, or behavior when the user has none saved, but with annotations carrying the read-only contract this is a solid contribution.

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?

A single em-dash-appended sentence that front-loads the action and resource, then spends the remainder on the two things an agent actually needs: what a template is and which tool consumes it. No filler.

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 zero-parameter read with no output schema, the description supplies the entity definition and the downstream tool, which is enough to call it correctly. Minor omissions are whether ordering or default/built-in templates are included, but nothing essential to invocation is missing.

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 tool takes zero parameters, so there is nothing for the description to disambiguate beyond confirming no filtering is required. Baseline 4 applies for a parameterless tool.

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 ('List the user's saved QR style templates') and immediately defines what a template is (reusable colors, shapes, center logo/emblem). It is clearly distinguishable from siblings like list_themes, list_profile_style_options, and get_qr_config by being scoped to QR style templates the user has saved.

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 routes the agent forward by naming apply_qr_template as the consumer of these templates, so the list-then-apply workflow is explicit. It does not state exclusions (e.g., 'do not use to fetch a single template' or 'built-in defaults are not included'), so it stops short of full when/when-not guidance.

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