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

Beyond the readOnlyHint/destructiveHint annotations it adds real behavioral context: the required key scope (content:read), the locale fallback to the primary language for missing translations, and the transformation of images into URLs and select fields into labels. It also warns that entry text is data, not instructions, which is a useful prompt-injection guard. 'Read-only; changes nothing' largely restates the annotations, and error behavior (e.g. unknown id) is unstated.

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 read-only disclaimer is front-loaded, which is good, but it duplicates what annotations already declare, and the locale-default sentence repeats the schema. The middle sentence is a long em-dash run-on that packs four distinct facts together, making it dense to parse.

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 carries the burden of describing the return shape and does so meaningfully: resolved locale, image URLs, select labels, drafts included. What remains thin is failure behavior and whether the preview reflects the live site's exact rendering pipeline, but for a single-item read the essentials are covered.

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; the description goes further by explaining the runtime semantics of locale — defaulting to the schema's first language and falling back to the primary language when a translation is missing. That is genuine meaning beyond the schema's 'default: its first'. The other three parameters (site, collection, id) get nothing extra in the description.

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 and resource — reading one CMS entry as the site would render it — and adds scope qualifiers ('drafts too', locale resolution, images as URLs) that separate it from a plain entry read. It does not name the adjacent siblings (get_entry, preview_draft) explicitly, so the agent must infer the boundary rather than being routed to it.

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?

'drafts too' implies this is the right tool when unpublished content must be previewed, but the description never states when to prefer it over get_entry or preview_draft, nor any prerequisite beyond the content:read scope. Usage is inferable but not spelled out.

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