wordpress_advanced_wp_db_query

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

With no annotations provided, the description carries the safety burden and effectively discloses the read-only constraint and allowed SQL statement types. However, it omits what happens when restricted operations are attempted, result format details, and timeout behavior.

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?

Two efficient sentences with clear front-loading of the operation. The '[UNIFIED]' prefix appears to be metadata noise but is brief; otherwise zero waste in the description structure.

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 high-complexity SQL execution tool with no output schema and no annotations, the description adequately covers safety constraints but lacks crucial invocation details (parameter formats, return structure) that would be necessary for correct usage.

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 for undocumented parameters. It implicitly clarifies 'query' through the description text but provides no semantics for 'site' (ID? URL? slug?) or 'max_rows' (truncation vs pagination 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?

The description clearly states the tool 'Execute[s] read-only SQL query' with specific allowed operations '(SELECT, SHOW, DESCRIBE only)', distinguishing it from sibling tools like wordpress_advanced_wp_db_import or repair which modify data.

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?

It implies usage context with 'For advanced users and debugging,' but lacks explicit guidance on when to choose this raw SQL approach versus higher-level WordPress tools like wordpress_list_posts or the sibling wordpress_advanced_wp_db_search.

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