wp_search_site

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

No annotations are provided, so the description must carry the full burden. It mentions 'comprehensive results and metadata' but fails to disclose important behaviors such as whether pagination is supported, the result format, or any rate limits. This leaves significant behavioral gaps for a read operation.

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 concise: a single sentence defining the purpose followed by focused usage examples. Each example demonstrates a distinct parameter combination. No wasted words, but the examples could be slightly trimmed without losing clarity.

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?

The description adequately explains the tool's core function and parameter use via examples. However, it lacks details on output format, error handling for missing terms, or limitations on search scope. Given the absence of an output schema, more context on results would improve completeness.

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 100%, so baseline is 3. The description adds value through usage examples that demonstrate how to combine parameters (e.g., `--type="posts"`), which clarifies the enum usage and the optional nature of `site`. This enriches parameter semantics beyond the schema alone.

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 it performs site-wide search for content across posts, pages, and media, with comprehensive results and metadata. This is a specific verb+resource that distinguishes it from sibling tools, none of which are search 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?

Usage examples explicitly show how to use the tool for general search and filtered by content type. While no explicit 'when not to use' is given, the examples provide clear context for common search scenarios.

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