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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so safety is covered. The description adds two useful behavioral facts: the content is publicly visible only and the response includes rendered HTML. It does not mention not-found or unpublished behavior.

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. It is efficient, though its brevity is part of why parameter and usage details are absent.

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 tool with an output format not formalized in an output schema, the description mentions rendered HTML but omits how kind/slug resolve, what happens for unpublished or missing content, and when to prefer the sibling fetch tools. Given 0% schema coverage, this leaves real gaps.

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% and the slug field has an empty description, so the description needs to compensate but does not. It never mentions 'kind' (posts vs pages) or 'slug', leaving both parameters unexplained beyond their names and enum.

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 publicly visible published snapshot), which is discernible from siblings like list_published or get_content. It does not explicitly differentiate itself from near-neighbors such as get_content or render_published, so it stays below 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?

No guidance on when to use this versus get_content, list_published, or render_published, all of which appear in the sibling list and sound closely related. The agent must infer selection from names alone.

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