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

Annotations already declare readOnlyHint=true and destructiveHint=false, so safety is covered. The description adds real value by disclosing the content scope of the reference (what topics are inside), but says nothing about return format, length, or whether the output is a document to read versus structured data. With annotations shouldering the safety profile, this is adequate but not rich.

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?

It is two sentences with the imperative usage instruction placed last, which is reasonable. The long topical enumeration is informative but dense — a dozen comma-separated items in one sentence — and borders on listing for its own sake where a shorter summary would carry the same signal.

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?

There is no output schema, so the description carries the burden of describing the return, and the topical enumeration does that job well. The gap is that it omits practical properties of the reference — format, size, whether it is paged — which matters for an agent deciding whether to pull the whole thing into context.

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 tool takes zero parameters, so the baseline is 4 and there is nothing for the description to disambiguate. It correctly avoids inventing parameter discussion.

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 names the resource precisely — the full reference of the template document — and enumerates the topics it covers (page, paragraphs, styles, formulas, bands, barcodes, grid, fonts). That makes it clearly distinguishable from siblings like get_template, list_templates, or preview_template. It never states an explicit retrieval verb, relying on the name/title, which keeps it just 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?

"Read it before you write or change a template body" gives a concrete trigger condition tied to the write-side siblings (create_template, update_template). It does not explicitly contrast with get_template or explain when reading this reference is unnecessary, so an exclusion clause is missing.

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