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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered externally. The description contributes the content-visibility filter, which is genuinely beyond the annotations, but says nothing about ordering, default page size, or how cursor exhaustion behaves.

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?

Two short sentences, zero filler, with the core capability front-loaded and the scope constraint immediately after. Nothing is redundant with the title or annotations.

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?

No output schema exists, so the description could reasonably describe the shape of returned items or pagination behavior, and it does neither. For a simple read-only list tool this is adequate but leaves the agent guessing about return contents.

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 33%: cursor is documented in-schema and kind is self-describing via its enum, but limit has no stated default or meaning beyond the 1-100 bounds. The description adds nothing about any of the three parameters, so it fails to compensate for the coverage gap.

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 ("List ... published posts or pages") plus a visibility qualifier ("publicly visible"), which is enough to tell it apart from generic list_content. It stops short of naming the sibling it differs from, so the differentiation relies on inference.

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 exclusion rule ("Private, subscriber-only and scheduled content is excluded") tells an agent when this is the right tool in a scoping sense, but there is no explicit statement of when to prefer it over list_content or get_published, and no prerequisites.

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