mainwp_sites_add

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

No annotations provided, so the description carries full burden. It does not disclose behavioral traits like whether duplicates are prevented, if existing connections are overridden, or authentication requirements. The simple statement 'Add a new WordPress site' hides important side effects and conditions.

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 sentence, extremely concise with no redundant words. However, conciseness here sacrifices completeness; while it's efficient, it could include more useful information without being verbose.

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 tool has 6 parameters (1 required), no output schema, and no annotations, the description is insufficient. It fails to explain return values, error scenarios, or how the addition process works (e.g., if it verifies connectivity). The agent lacks context to handle potential failures.

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 coverage is 100%, so parameters are already described with name, type, and purpose. The description adds no additional meaning or context about which parameters are critical or how they interact. Baseline 3 is appropriate.

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 action ('Add a new WordPress site') and the target system ('MainWP Dashboard'), using a specific verb and resource. It distinguishes from sibling tools like mainwp_sites_edit or mainwp_sites_remove, so the agent can infer this is for creation.

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 on when to use this tool versus alternatives. The description does not mention prerequisites, such as whether a site must be installed with MainWP Child plugin, or when to use add vs. edit vs. reconnect. This leaves the agent with no context for decision-making.

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