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 that the payload is raw HTML + Liquid source (not rendered output) and that omitting path returns everything, but says nothing about response size or shape for a multi-file pull, which is the main behavioral risk here.

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?

A single front-loaded sentence with no filler; the resource and the toggle condition both land immediately.

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 2-parameter read tool with full schema coverage and annotations, this covers what is needed to invoke it correctly. The remaining gap is the return shape when all files are requested (single string vs. a per-file collection), which matters since no output schema exists, but it is a minor omission.

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 100%, so the baseline is 3, but the description adds value the schema does not: it makes explicit that 'path' selects exactly one file and that omitting it returns all files, whereas the schema only says 'One file's text.' That default-behavior clarification is genuine additive meaning.

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 (a stock template's HTML + Liquid files) with a clear scope qualifier: all files, or one selected by path. It implicitly separates itself from read_site_file/write_site_file by saying 'stock template,' but it never names list_templates, which an agent would need to discover slugs.

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?

The '(all, or one with path)' clause explains internal usage of the optional parameter, not when to reach for this tool rather than list_templates or read_site_file. Usage is inferable but no explicit when/when-not guidance or prerequisites (e.g., needing a slug from list_templates) are given.

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