wp_search_content

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

No annotations are provided, so the description carries full burden. It only states 'Search across...' but does not disclose that the tool is read-only, or any behavioral traits like idempotency, permissions needed, or side effects. The description fails to add behavioral context beyond the basic action.

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 with no wasted words. It is front-loaded with the action verb 'Search' and immediately specifies the scope. Every part of the sentence 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 the tool has 6 parameters including query, filters, and limit, the description only lists content types. It does not explain query usage, date filtering, status, or pagination. No output schema exists, so the description needed to provide more completeness for agent invocation. It is inadequate for the complexity.

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 33% (only query and post_type have descriptions). The overall description does not mention any parameter details or provide additional meaning beyond the schema. With low schema coverage, the description should compensate, but it only lists content types without parameter semantics.

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 tool searches across multiple WordPress content types (pages, posts, media, categories, tags), using a specific verb ('Search') and resource list. It distinguishes from sibling CRUD tools (create, delete, update) by being a search operation.

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 description implies the tool is for searching content but does not explicitly state when to use it versus alternatives. No exclusions or alternative tool references are provided. Sibling tools are mostly CRUD, so context is clear but guidance is lacking.

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