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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is covered. The description adds value the annotations cannot: it discloses the return shape (links plus a short summary) and that results are curated guide content rather than generated answers. It stops short of mentioning result-count behavior or the default limit, which keeps it off a 5.

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 sentences, zero filler, with the trigger condition front-loaded before the return description and the sibling routing last. The parenthetical topic list is long but earns its place by covering the tool's domain scope and hinting at the topic enum.

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?

With no output schema, the description correctly takes on the job of explaining what comes back (links plus summary), and with zero required parameters the call semantics are simple. The only shortfall is that limit/paging behavior and the topic vocabulary are left implicit, which matters modestly for a low-coverage 3-parameter schema.

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 33%; only 'query' has an inline example, while 'limit' and 'topic' are undocumented structurally. The parenthetical topic list (AI/MCP, images and media, speed and database, SEO, security, fixing errors) roughly maps to the topic enum values, giving partial compensation, but it never states that these are the topic parameter values and says nothing about limit. Net: some meaning added, clear gap remaining.

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 action (returns links to hands-on guides with a short summary) plus the resource (step-by-step help for common WordPress tasks) and enumerates covered domains. The closing clause explicitly separates it from wp_docs (API/function reference), so an agent can route between them without opening either schema.

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?

Opens with an explicit trigger ('Use when the user wants step-by-step help with a common task') and names the alternative with the condition that selects it ('For an API or function reference, use wp_docs'). Both when-to-use and when-to-use-something-else are present, not inferred.

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