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

The description frames this as a pure read ("Explore...", "Returns a sitemap-like overview"), but the annotations declare readOnlyHint=false and idempotentHint=false, i.e. a non-read mutation-capable tool. This direct conflict about the tool's core safety trait is a serious mismatch that will confuse an agent's planning.

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, no waste: the first states purpose and return shape, the second states usage. Purpose is front-loaded and every clause earns its place.

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 compensates by naming what is returned (pages, posts, menus, URLs). Parameters are fully covered by the schema. The only shortfall is that the annotation conflict leaves the agent unsure about side effects, but the descriptive content itself is nearly complete for a read-oriented tool.

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 100% – scope, site_id, and per_page are each fully documented with defaults and the scope enum described inline. The description adds no parameter detail beyond what the schema already states, so 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 verb+resource is specific: "Explore the structure of a WordPress site" and it concretely describes the payload ("sitemap-like overview: pages, posts, menus, and their URLs"). This differentiates it from the single-resource listers (wp_list_pages, wp_list_posts, wp_list_menus) by framing it as an aggregated overview, though it never names those alternatives explicitly.

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?

Clear when-to-use context: "understand the site layout before making changes, or to find the right page/post to edit." It gives two concrete scenarios but offers no exclusions or comparison against the sibling list tools, so an agent must still infer when a targeted wp_list_pages call is preferable.

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