Toggle Maintenance

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only states 'Toggle maintenance mode on/off' without detailing side effects, reversibility, or impact on the site. There is no mention of what happens to visitors or whether the toggle is a safe operation.

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 short sentence that is easy to parse and front-loaded with the action. It is not verbose, but it is appropriately sized for a simple toggle operation, though it could benefit from a bit more context.

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?

The tool has two required parameters and no output schema or annotations. The description provides no information about expected return values, error conditions, or how to verify the toggle succeeded. For a mutation operation, this leaves significant gaps.

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 input schema already provides descriptions for both parameters ('WordPress software identifier' and 'Hosting account username'), covering 100% of parameters. The description adds no extra meaning beyond the schema, which is the baseline when schema coverage is high.

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 'Toggle maintenance mode on/off' clearly identifies the specific action (toggle) and resource (maintenance mode). It distinguishes from the sibling tool wp_maintenance_status, which presumably only reads the status, making the purpose unambiguous.

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 for toggling maintenance mode, but it does not explicitly state when to use this tool versus alternatives, such as checking status with wp_maintenance_status. There are no exclusions or context cues beyond the action itself.

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