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

Annotations already declare readOnlyHint=true and destructiveHint=false, so 'READ-ONLY' adds little on its own; however the description goes beyond them by disclosing returned fields (including 'last error') and by clarifying the connection setup requires an Application Password with no plugin. It stops short of describing ordering or empty-list response shape, so not a full 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?

Three tight sentences with the safety marker and the return-field inventory front-loaded before the routing advice. The leading 'READ-ONLY.' duplicates the readOnlyHint annotation and the title restates the name, a minor bit of unearned text, but no sentence is wasted otherwise.

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 compensates by naming the fields the call returns, and it covers the zero-result case with remediation steps. For a no-parameter prerequisite listing tool this is fully sufficient for an agent to invoke and act on the result.

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 no argument semantics to document; baseline is 4. Nothing in the description is needed to explain inputs, and it correctly implies no filtering arguments exist.

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 (list) and resource (WordPress sites/blogs connected to the Vendooly organization) and enumerates the fields surfaced (site_id, URL, WordPress user, status, last error). The prerequisite framing 'every other wp_* tool needs site_id' cleanly separates it from wp_list_posts, wp_list_terms, and the woo_* siblings.

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 explicit ordering guidance ('Call it first') plus a concrete fallback path when the result is empty, routing the user to Settings → Integrations → Connect WordPress blog. Both the when-to-use and the when-nothing-is-found branch are covered, leaving nothing to infer.

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