wordpress_execute_sql

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

With no annotations, the description carries the full burden. It discloses a key behavioral constraint—only SELECT, SHOW, DESCRIBE, and EXPLAIN are permitted—effectively making it a read-only SQL executor. However, it does not mention result formatting, error behavior, or permission requirements.

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?

One short sentence, front-loaded with the action and immediately followed by the safety constraint. No wasted words and the most important information is presented first.

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?

Given the tool's simplicity, the description is adequate but incomplete: it lacks any mention of the return value (result set) and error handling. The safety restriction is helpful, but the absence of output schema behavior leaves some ambiguity about what the agent can expect.

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 single 'query' parameter is named clearly, and the description adds meaning by restricting acceptable query types. It does not, however, provide format details (e.g., whether semicolons are allowed, if multiple statements are supported, or if a trailing semicolon is required).

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 action (Execute) and object (SQL query), and explicitly enumerates the allowed statement types (SELECT, SHOW, DESCRIBE, EXPLAIN), distinguishing it from all other WordPress tools that perform specific operations rather than raw SQL execution.

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 implies it is for safe, read-only custom SQL queries via the 'only for safety' clause, but it does not explicitly state when to use this tool versus the many specialized WordPress tools (e.g., get_posts, list_tables) or mention any alternatives.

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