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

Annotations already establish that this is a read-only, idempotent, non-destructive, closed-world operation. The description adds concrete behavioral context beyond annotations: preview_url links are anonymous and expire after 30 minutes, and an eligible API plan is required.

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 description is two compact sentences with no filler. The core action is front-loaded, followed by the useful expiration and plan caveats.

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?

This is a read-only list tool, so annotations cover the safety profile, and no output schema exists. Still, with low parameter description coverage, the description should say more about filtering, pagination, and limit behavior to fully equip an agent calling it.

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 only 25%, with just the cursor parameter documented. The description mentions posts/pages and draft/published scope, which loosely maps to kind and status, but it does not explain limit bounds/defaults, cursor pagination behavior, or the required kind parameter's role.

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 states a specific verb and resource: listing draft and published editor posts or pages. It distinguishes the scope from published-only siblings implicitly by including drafts, but does not explicitly name alternatives such as list_published or get_content.

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?

Usage is implied by the draft/published list scope, and the description notes an eligible API plan requirement. However, it does not say when to choose this tool over siblings like list_published, search, or get_content.

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