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

Annotations already declare readOnlyHint=true, openWorldHint=true and destructiveHint=false, so the description's added 'LIVE from the WordPress site' meaningfully distinguishes live reads from cached data, and 'newest first' discloses ordering. It also flags that post_id mode returns full HTML content, which is a substantive behavioral detail beyond the annotations.

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?

Three compact sentences with the read-only/live qualifier front-loaded, followed by return fields, then filters, then the special post_id case. No filler, and the most decision-relevant facts come first.

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 five parameters, no output schema and full schema coverage, the description fills the important gap by enumerating return fields and explaining the two modes. It omits pagination/offset behavior and how the 200 cap interacts with large result sets, a minor gap for a list tool.

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, but the description adds real meaning: post_id changes the return shape entirely (single post with full HTML content) rather than merely filtering, and status values are enumerated in prose. It does not add syntax hints for search beyond what the schema states.

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 ('Blog posts ... newest first') and enumerates the returned fields (id, status, title, slug, link, dates, categories, tags, excerpt, content length), so an agent knows exactly what it gets. It also distinguishes the two modes (list vs. single post via post_id), which separates it from mutation siblings like wp_update_post.

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?

Gives explicit conditional guidance for the post_id mode: 'use it before wp_update_post', which tells the agent to read before writing. Filter usage (status, search) is described but there is no explicit statement about when to prefer wp_list_terms or other listing siblings, so routing guidance is clear but not exhaustive.

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