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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description usefully adds that results are scoped to the calling key's workspace (implying permission-dependent results), but says nothing about pagination, result limits, or ordering. With light annotations, the description adds some value without fully carrying the behavioral burden.

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 sentences, no filler: the first establishes scope, the second establishes the follow-up action. Scope is front-loaded and the actionable guidance comes second.

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 single optional parameter, read-only listing tool with no output schema, the description covers scope and the reason to call it. It stops short of describing what a returned record contains (id, name, theme, layout system), which would help an agent consume the result, but it is adequate overall.

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?

There is one optional parameter ('query') and schema description coverage is 100%, so the schema already documents it fully. The description does not mention the search parameter at all, 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 ('List the templates') plus the scope of what is returned ('visible to this key's workspace (built-ins and workspace templates)'). It does not explicitly differentiate itself from sibling list tools like list_themes or list_packaging_models, so it falls short of a 5.

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?

Gives clear usage context by naming the downstream consumer: pass an id as generate_presentation's templateId. That tells the agent exactly when this tool is needed, though there are no exclusions or negative conditions.

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