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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds genuinely useful scope information (shared workspace templates plus company-owned templates), which is context the annotations don't convey. It says nothing about pagination, ordering, or result shape, so it stays at an adequate 3.

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?

One sentence, no filler, and the scope qualifier is front-loaded immediately after the verb. Nothing in it is redundant with the title or annotations.

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 simple read-only list tool with full schema coverage and annotations covering safety, the description is close to sufficient. The only mild gap is that there is no output schema, so an agent gets no hint about the shape of returned templates, though this is minor for a list endpoint.

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 the single qrType parameter is fully enumerated with a description, so the schema carries the load. The description never mentions qrType or its filtering effect, so it adds nothing beyond the structured data — 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?

States a specific verb and resource ('List QR templates') and adds scope ('shared workspace templates plus your company's own'), which tells an agent what the result set contains. It does not explicitly differentiate itself from sibling templates_get, but the plural list verb makes the distinction inferable.

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?

There is no guidance on when to call this versus templates_get or templates_create, and no mention of how the qrType filter affects results. 'you can use' hints at the intent but stops short of any explicit when-to-use or exclusion.

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