wordpress_advanced_wp_db_search

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

No annotations provided, so description carries full burden. While 'search' implies read-only, it doesn't explicitly confirm non-destructive behavior, disclose performance implications for large databases, or describe output format (no output schema exists). Missing critical safety and operational context for a database tool.

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?

Brief two-sentence structure is efficient, but the '[UNIFIED]' prefix appears to be implementation metadata rather than user-facing documentation, creating noise. Given the complete lack of parameter documentation, the description is actually underspecified rather than appropriately concise.

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?

Inadequate for a 6-parameter tool with zero schema descriptions and no output schema. The description omits parameter details, return value structure, pagination behavior, and safety confirmations that are essential for a database search utility.

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 0% schema description coverage, the description fails to compensate. Only implies 'search_string' through the phrase 'search for specific strings'. No explanation of 'site' identifier format, 'tables' array structure, 'regex' syntax, or default 'max_results' behavior.

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?

States specific action (search) and target (database for specific strings) clearly. However, lacks differentiation from siblings like 'wordpress_advanced_wp_db_query' or 'wordpress_wp_search_replace_dry_run', leaving ambiguity about when to choose this over SQL queries or dry-run replacements.

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?

Lists applicable use cases (finding content, debugging, data migration) but provides no guidance on when NOT to use it, prerequisites (e.g., database permissions), or which sibling tool to use for related operations like replacement or structural queries.

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