wp_search_site

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. However, the description does not mention whether the tool is read-only (although searching is safe), any potential side effects, authentication requirements, or rate limits. The phrase 'comprehensive results and metadata' hints at the return but lacks depth.

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 a clear purpose sentence followed by illustrative usage examples. While the examples are somewhat repetitive (each follows the same pattern), the overall length is appropriate and each line serves to demonstrate a specific parameter usage.

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 search tool with no output schema and no annotations, the description should provide more detail about the return format (e.g., list of results, pagination, metadata structure). The phrase 'comprehensive results and metadata' is vague. Given the simplicity of the parameters and task, the description could be more complete.

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 input schema provides full descriptions for all three parameters (100% coverage), so the baseline is 3. The usage examples in the description add practical context (e.g., how to specify types) but do not add critical semantic meaning beyond what the schema already conveys.

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 uses the specific verb 'performs a site-wide search' and clearly identifies the resources (posts, pages, media) and the outcome (comprehensive results with metadata). This clearly distinguishes it from sibling tools like wp_get_media or wp_delete_post, which are content-specific operations.

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 does not explicitly state when to use this tool versus alternatives. While it provides usage examples demonstrating different content types, it lacks guidance on when not to use it (e.g., for very specific retrievals) or mentions of alternative tools for different tasks. The implied context is adequate but not explicit.

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