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

Annotations cover the safety profile, but the description adds real behavioral context beyond them: the capability requirement, the exact allowlist composition including the filter hook, redaction of credential-like keys and values, and the honest caveat that a short random value under an ordinary name is indistinguishable and will be returned. That last disclosure is exactly the kind of edge-case behavior an agent cannot get from annotations or schema.

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?

Front-loaded with purpose, capability, then the allowlist and redaction rules — the ordering is right. The parenthetical site tag and the trailing "Through Royally: read-only, runs straight away" are boilerplate that restates the readOnly annotation.

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 only two parameters and no output schema, the description covers what an agent needs to call it successfully: permission, valid inputs, redaction behavior, and safety. It stops short of saying what happens on a non-allowlisted option name (error vs. empty result), which would close the last gap.

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 coverage is 50% and the `name` parameter has no schema description at all, so the description carries that burden: it enumerates the 13 default readable options and explains the filter and admin-allowlist extensions of the valid domain. `site_id` is left to the schema, which already documents it with an enum.

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 ("Get a single WordPress option value"), which is precise enough to separate it from aggregating siblings like wp_get_site_info or wp_get_plugin_settings. It does not name wp_update_option as the write counterpart, so the read/write distinction is only implied by the verb.

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 concrete preconditions: manage_options capability and an allowlist membership requirement, including the conditional case (admin-allowlisted plugin options only while option writes are enabled). It never names an alternative tool or says when to prefer a different retrieval tool, so routing guidance is incomplete.

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