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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered. The description adds only that 'public stats' are included in the response, which is a small amount of context beyond structured fields and says nothing about error behavior for missing slugs.

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, front-loaded with the resource and scoped by the key. It is efficient with no filler, though the '+ public stats' phrasing is slightly telegraphic rather than fully clear about the return payload.

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 one-parameter read-only getter with annotations covering safety, the definition is close to sufficient. However, there is no output schema, so 'full details + public stats' is the only description of the return value and remains vague about what fields those comprise.

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 coverage is 0% for the single parameter, so the description must carry the load; saying 'by slug' does clarify that the identifier is a slug rather than an ID or name, which is genuinely useful. It stops short of any format, casing, or length guidance for the slug value.

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 action and resource: retrieve a single template, keyed by slug, including details and public stats. The word 'single' implicitly contrasts with the sibling templates_list, so an agent can distinguish list vs. get without opening schemas, though no sibling is named explicitly.

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?

Usage is only implied: you need a slug, so this is the follow-up call after a list. There is no explicit statement of when to prefer this over templates_list or what to do if the slug is unknown.

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