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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, and the description mostly restates that ('read-only'). The only genuine addition is 'runs straight away', implying no approval gate or kill-switch interception, plus the concrete site binding — useful context in a fleet environment but thin given the annotations already carry the safety profile.

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 the returned field list and routing rule in the first sentence, with the alternative in the second. Slightly padded by the parenthetical site echo and the 'read-only' restatement that duplicates annotations, but no sentence is wasted on substance.

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?

For a no-required-param read tool with no output schema, the description effectively serves as a return-value contract by listing the six fields returned, and it covers the sibling routing. It does not mention multisite/network scope or how the default site is resolved when site_id is omitted, which keeps it short of perfect.

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% and the single optional site_id parameter is documented with its enum value and URL in the schema itself. The description adds nothing about the parameter, so baseline 3 applies.

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 user-facing site metadata') and enumerates exactly which fields are returned (name, description, URL, language, timezone, WP version). It explicitly names the sibling wp_get_site_status as the tool for the operator-facing counterpart, so an agent can distinguish the two 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?

Gives an explicit routing rule: use this for user-facing metadata, use wp_get_site_status for PHP/MySQL versions, plugin count, memory limits and disk free. Both the when and the when-not with a named alternative are present.

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