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

With readOnlyHint/openWorldHint already present, the description still adds substantial context: it enumerates exactly which versions, write paths and conditions are returned and explicitly lists what XeoRank cannot do (PHP filters, template editing via page tools). The destructiveHint=true annotation is inconsistent with this otherwise pure-discovery framing, though the description itself makes no destructiveness claim.

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?

A single dense sentence with the actionable directive ('call this before...') front-loaded and the payload contents listed afterward. Everything earns its place, though the long run-on parentheticals make it heavier to parse than necessary.

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?

There is no output schema, so the description carries the burden of explaining returns – and it does so thoroughly, listing versions, all five write paths with conditions, the V4 element list, and known limitations. Complete enough to act on; only the destructive/read annotation ambiguity remains unexplained.

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?

Only one parameter (site_id) and schema description coverage is 100%, so the schema already documents it fully (including pointing to list_wordpress_sites). The description adds no additional syntax or source detail beyond that, which is the expected baseline when the schema does the work.

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 purpose: report what actually exists on the WordPress site and which XeoRank write path applies, naming the concrete returned artifacts (connector/Elementor versions, five write paths, unsupported operations). This clearly separates it from generic siblings like get_wordpress_site or list_wordpress_sites, though the framing ('WHAT ACTUALLY EXISTS... which path does it') is slightly oblique rather than a crisp verb+resource statement.

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?

Gives an explicit usage trigger – 'call this before concluding anything is not supported' – which tells the agent when this tool is the right call. It does not name an alternative sibling or state when-not to use it, so it stops short of full routing guidance.

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