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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is covered. The description adds genuine value with the zero-results behavior (walk the user through setup), but says nothing about what a returned site record contains — no mention of site IDs or names an agent would need for follow-up calls.

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?

Two short sentences, front-loaded with the core action, and every sentence carries a distinct piece of information. The phrase "for a requested WordPress task" is the only soft spot — it is filler relative to the concrete statement around it.

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?

For a simple zero-param read tool with full annotation coverage, the definition is close to sufficient, and it usefully covers the empty-state path. The notable gap is the absence of an output schema combined with no description of what a site entry looks like, which matters because downstream tools presumably need a site identifier.

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 tool takes zero parameters, so there is nothing for the description to disambiguate; the baseline for a parameterless tool applies. No misleading or contradictory parameter guidance is present.

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?

States a specific verb and resource ("List connected WordPress sites") that is clearly distinct from the wp_list_* siblings which list posts, menus, widgets, etc. The trailing qualifier "for a requested WordPress task" is vague and adds no discriminating information, keeping it from a 5.

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?

Implies usage context (call it to discover sites before performing a WordPress task) and explicitly handles the empty case by telling the agent to guide the user through setup. However, it never states when not to use it or which tool to call next with a returned site, leaving the agent to infer the workflow.

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