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

Annotations already establish readOnlyHint=true, destructiveHint=false, and idempotentHint=true, so the safety profile is covered. The description adds behavioral context beyond annotations: it states the output is HTML, and it warns about Foundry VTT stripping <style> tags, implying the returned HTML may include style tags that must be converted to inline attributes. This practical context about output format and constraints adds value without contradicting annotations.

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?

The description is compact and front-loaded: the core purpose is in the first sentence, followed immediately by usage constraints and downstream actions. Every sentence carries essential information, and there is no redundancy with annotations or schema. It's efficient and well-structured.

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-parameter retrieval tool with robust annotations (read-only, idempotent), the description fully equips the agent: it explains what the output is (full HTML), how to use it (as style reference, not copy), and what to do next (generate variation, save via journal-page-create with 'text' type). There's no output schema, but the description covers the return value sufficiently for the agent's task. Nothing essential 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 input schema has one parameter, templateId, with description 'Template ID from handout-template-list' which already fully explains its meaning and source. Since schema_description_coverage is 100%, the description adds no additional parameter-specific information. Baseline 3 is appropriate; the tool description doesn't need to repeat schema content.

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?

The description clearly states the tool's purpose: 'Get the full HTML of a handout template.' It uses a specific verb ('get'), names the resource ('handout template'), and adds that it returns full HTML. This distinguishes it from the sibling handout-template-list, which presumably returns metadata or IDs. The unique purpose is unambiguous.

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?

Explicit guidance is given: 'Use this as a STYLE REFERENCE — do not copy it verbatim.' It then instructs the agent to generate a unique variation and save via journal-page-create, including implementation details like inline styles because Foundry VTT strips <style> tags. This tells the agent exactly when and how to use the tool, and what to do with the result. No other tool has similar guidance in the sibling set.

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