wordpress_wp_db_optimize

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

With no annotations provided, the description carries the full disclosure burden. It successfully explains the mechanism (OPTIMIZE TABLE SQL command) and scope (all tables), but omits critical behavioral traits like table locking implications, potential downtime, execution duration estimates, or whether the operation is reversible.

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 brief (two sentences), but contains metadata noise '[UNIFIED]' that doesn't aid the agent. The first sentence largely restates the tool name, while the second sentence carries all substantive behavioral information, resulting in suboptimal front-loading.

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 database maintenance tool with no output schema and no annotations, the description adequately covers the core function but lacks execution context. It should mention safety considerations like temporary table locks, maintenance mode recommendations, or backup advisories that are standard for production database optimization operations.

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 0% (the 'site' parameter is entirely undocumented in the schema). The description fails to compensate by explaining what 'site' means—is it a domain, site ID, or path?—or providing an example. This leaves the single required parameter semantically ambiguous despite the description being present.

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 specifies the action (Optimize), resource (WordPress database tables), mechanism (runs OPTIMIZE TABLE), and effects (reclaim space, improve performance). This precisely distinguishes it from siblings like wordpress_wp_db_check, wordpress_advanced_wp_db_repair, and wordpress_wp_db_export which perform different database 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 implies usage through the specificity of 'all WordPress tables,' helping distinguish it from table-specific operations. However, it lacks explicit guidance on when to use this versus alternatives, prerequisites like database access permissions, or warnings about when NOT to use it (e.g., during high traffic).

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