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

Annotations already cover read-only, idempotent and non-destructive behavior, so the bar is lower; the description still adds real value by disclosing what is NOT returned (no theme, header, footer, styles, scripts) and that private, scheduled and subscriber-only content is excluded. It does not mention auth requirements or error 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?

Four tight sentences, each carrying distinct information: purpose, return contents, omissions, and exclusions. Front-loaded with the core action and no filler.

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 usefully enumerates the response (snippets, footnotes, summary, TOC, featured image, SEO metadata) and exclusions, which is most of what an agent needs. The remaining gap is the unexplained slug parameter.

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 description is empty, so the description is the only source of param meaning. 'Post or page' loosely maps to the kind enum, but neither the enum values nor what slug identifies (and its format/source) is explained.

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 (render) and resource (public post or page content) and specifies the output form (an HTML fragment for a customer-owned layout). It does not explicitly differentiate itself from the close sibling get_published, so the agent must infer the boundary.

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?

'For a customer-owned layout' implies the decoupled/headless use case, but no explicit when-to-use, when-not, or named alternative (e.g. get_published vs render_published) is given. Usage is implied rather than stated.

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