Set AI Option Status

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

With no annotations, the description carries the full burden of behavioral disclosure. It only states the action (enable/disable) without explaining what 'AI tools' encompasses, whether the operation is reversible, what permissions are needed, or what the response or side effects might be. This is a significant gap for a state-changing 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?

The description is a single, clear, and front-loaded sentence with no wasted words. It effectively communicates the core action and target, making it easy for an agent to parse quickly.

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 simplicity of the tool, the description is still not complete. It does not explain what 'AI tools' refers to in the WordPress context, how the username and software parameters identify the target, or what the result of the operation is. With no output schema and no annotations, the agent is left without sufficient context to reliably invoke the tool.

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 100%, so the schema already documents each parameter. However, the descriptions are terse (e.g., 'WordPress software identifier', 'Hosting account username') and the tool description adds no extra meaning. The baseline of 3 applies because the schema handles the documentation, though richer descriptions would improve clarity.

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 verb 'enable or disable' and the resource 'AI tools for WordPress', making the tool's function immediately obvious. It distinguishes itself from sibling tools like wp_ai_status (which likely queries status) and other toggles by specifying the target as AI tools.

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?

There is no guidance on when to use this tool versus alternatives. It does not mention checking status first with wp_ai_status, nor does it indicate prerequisites or scenarios where toggling AI tools might be inappropriate. The usage context is only implied by the tool name and description.

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