Search content

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

Annotations already establish read-only, idempotent, non-destructive behavior, but the description adds important context: it requires edit_posts, excludes trash/auto-draft/excluded types, includes readable drafts and private entries, returns summaries without content, and does not paginate beyond per_page. These are substantive behavioral disclosures 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?

The description is front-loaded with the search action, scope, and result shape, then adds authorization and pagination constraints without filler. Every sentence contributes operational information.

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?

There is no output schema, but the description explains the return shape, summary nature of results, permission requirements, status inclusion/exclusion, and pagination limits. It also points to wp_list_posts for filtered/paged listing, so an agent has enough to call this correctly.

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?

With 100% schema description coverage, the baseline is 3. The description adds useful meaning: query searches title, excerpt, and content; type spans all searchable post types or one; and per_page caps results with no further pages.

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 states a specific verb and resource set: searching posts, pages, and other entries for words in title, excerpt, and content, ordered by relevance. It also scopes the search by post type and status, making clear this is a search operation rather than a list/get 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 gives clear usage context: it searches across all searchable post types or one, includes drafts/private entries subject to read permissions, and notes that wp_list_posts also supports search with filters and paging. The alternative is implied rather than stated as an explicit rule, so it falls just short of a 5.

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