wordpress_enable_maintenance_mode

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

With no annotations, the description must disclose behavioral traits, but it only repeats the action. It fails to explain how the tool decides between enabling and disabling given the empty parameter schema, nor does it mention effects on site access or whether it toggles state. This is a serious transparency gap.

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 concise sentence, front-loaded with the verb and resource, with no filler words. However, its brevity contributes to the under-specification of behavior, so it doesn't earn a top score.

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 having no parameters and no output schema, the tool's behavior is not adequately specified because the enable/disable dichotomy is unresolved. The description lacks any mention of preconditions, side effects, or return values, making it insufficient for an agent to use the tool correctly.

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 has zero parameters, so the description must clarify the tool's operation, but it doesn't. The phrase 'Enable or disable' implies a choice that no parameter can express, leaving ambiguous whether the tool toggles the current state or requires some external context. The empty schema baseline is 4, but the misleading implication drops the score.

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 uses a specific verb phrase 'Enable or disable' with a clear resource 'WordPress maintenance mode,' identifying exactly what the tool does. The tool is unique among the large sibling set; no other tool mentions maintenance mode, so it is clearly distinguishable.

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?

No guidance is provided on when to enable vs disable maintenance mode, or when this tool should be preferred over any alternative. The description only restates the function, leaving usage decisions entirely to the agent.

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