wordpress_wp_db_optimize

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

With no annotations, the description carries full burden. It mentions running OPTIMIZE TABLE, implying a write operation, but fails to disclose potential table locking, performance impact, required permissions, or that it affects all tables across the site.

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 two sentences, front-loaded with the core action and an explanatory second sentence. No wasted words.

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?

Despite being a database optimization tool, the description lacks details on return values, duration, side effects, or prerequisites. Given no output schema, it should explain what the agent can expect after execution.

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 only parameter 'site' has no schema description (0% coverage). The description does not explain what 'site' represents (e.g., ID, URL), so it adds no meaning beyond the schema.

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 optimizes WordPress database tables by running OPTIMIZE TABLE on all tables, specifying the verb 'optimize' and resource 'database tables'. It distinguishes from sibling tools like wordpress_wp_db_check and wordpress_wp_db_export.

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 provides no guidance on when to use this tool versus alternatives like wordpress_wp_db_check, nor does it mention prerequisites, risks, or scenarios to avoid (e.g., high traffic periods).

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