wordpress_search_posts

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

With no annotations, the description carries the burden. It states it searches in title and content, which is helpful, but does not explicitly declare that it is read-only or mention any limitations (e.g., search semantics, pagination behavior, result ordering). The 'Returns: Search results' is minimal. Adequate but not rich.

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?

Extremely concise—two sentences for the core purpose plus a brief Args/Returns list. Front-loaded with the action, no filler or redundant details. Every piece earns its place.

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 its simplicity and presence of an output schema, the description covers the basics but lacks nuances like search result sorting, pagination defaults beyond schema, or any note about query limitations. It's enough for a basic call but not fully complete for an agent that might need to filter or interpret results.

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?

The description adds little beyond the schema: it repeats parameter names and quotes defaults (from schema) with basic one-line hints like 'Search keyword' and 'Page number'. With 0% schema description coverage, it fails to enrich understanding (e.g., what 'search in title and content' means for keyword matching, or whether page is 1-indexed).

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?

Clearly states it searches WordPress posts by keyword in title and content, which is specific and distinguishes it from sibling tools like wordpress_list_posts (lists all) and wordpress_get_post (fetches one). The verb 'search' and resource 'posts' are precise.

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. It does not mention that it is for filtering by keyword unlike list_posts, nor does it suggest when not to use it. Usage context is entirely implied.

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