wordpress_get_posts

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions 'advanced filtering' but fails to specify critical traits like whether this is a read-only operation, potential rate limits, authentication needs, or what happens with invalid parameters. This leaves significant gaps for a tool with 5 required parameters.

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 a single, efficient sentence that front-loads the core purpose. It avoids redundancy and wastes no words, though it could benefit from more structure to separate filtering examples from general behavior.

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?

Given the complexity of 5 required parameters, 0% schema coverage, no annotations, and no output schema, the description is inadequate. It provides a high-level overview but lacks details on parameter usage, return values, error handling, or behavioral constraints, making it incomplete for effective tool invocation.

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%, so the description must compensate by explaining parameters. It lists filtering options like 'search, author, categories, tags, status, ordering', but these don't map directly to the 5 schema parameters (perPage, page, status, orderby, order). The description adds some context but fails to clarify parameter meanings or usage, leaving most semantics undocumented.

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 clearly states the verb 'Get' and resource 'posts' with the scope of 'advanced filtering', making the purpose evident. It distinguishes from siblings like 'wordpress_get_post' (singular) and 'wordpress_search_posts' by emphasizing filtering capabilities, though it doesn't explicitly contrast with all similar tools.

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?

No explicit guidance on when to use this tool versus alternatives like 'wordpress_search_posts' or 'wordpress_get_post'. The mention of 'advanced filtering' implies usage for complex queries, but lacks specific conditions, exclusions, or prerequisites, leaving the agent to infer context.

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