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

Annotations already establish readOnly, idempotent, non-destructive, and closed-world behavior, and the description adds value beyond them: it warns that content is untrusted reference data subject to 'Safe Static rules' and clarifies that reuse does not alter the owner's default style or publish a page. This is useful behavioral context an annotation cannot express.

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?

Four short sentences, purpose front-loaded, no wasted filler. The 'preserve task facts and Safe Static rules' phrasing is internal jargon that costs a little clarity but is not padding.

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?

With no output schema, the description does the work of indicating what comes back (the sanitized example deck when includeHtml is set) and flags the content as untrusted. It could say more about what is returned when includeHtml is false, but it is otherwise adequate for a two-parameter read tool.

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 0%, so the description must carry the load. It explains includeHtml's effect well (retrieves the complete sanitized example deck), but the required templateId is never described, and its UUID format/ownership constraint is only implicit in 'owner-private'.

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 (Read) and resource (owner-private template), and the 'owner-private' qualifier distinguishes it from the public sibling list_templates/preview_template. It stops short of explicitly naming which sibling to use instead, so it is clear but not fully differentiated.

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 a concrete condition for the optional parameter ('Set includeHtml to retrieve its complete ... example deck for reuse'), which is real usage guidance. However, it never says when to call this versus preview_template, list_templates, or get_recipe, leaving the sibling-selection decision to inference.

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