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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is covered. The description adds value by enumerating returned fields (title, status, date, excerpt, categories, tags) since no output schema exists, but it omits pagination behavior and default result size, which matter for a 10-parameter list tool.

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 tight sentences with the core purpose front-loaded and no filler. The second sentence about return fields slightly overlaps the schemaless return question but earns its place given there is no output schema.

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 10-parameter, filter-heavy list tool with no output schema, the description covers the basics (what is listed, what comes back) but never addresses pagination scope, default limits, or how to disambiguate from the many other list_* siblings. Just enough to call it, not enough to call it confidently.

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 100%, so all ten parameters including enums, ranges, and the per_page default are already documented in the schema. The description only hints that filters exist and lists some return fields, adding no syntax or constraint detail beyond the schema; baseline 3 applies.

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 gives a clear verb+resource ("List WordPress posts") and names the filter capability, so the agent knows exactly what it fetches. It does not, however, distinguish itself from near-siblings like wp_list_custom_posts, wp_list_pages, or wp_search_content, leaving the agent to infer that this tool is only for the built-in 'post' type.

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?

"with optional filters" implies the tool can be narrowed but gives no when-to-use guidance, no prerequisites, and no routing to alternatives (e.g. wp_search_content for keyword search, wp_list_custom_posts for CPTs). The agent must derive the usage context entirely from the sibling names.

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