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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so the agent knows this is a safe, non-mutating, externally-backed call. The description adds nothing behavioral beyond that, for example whether it requires elevated credentials, whether the plugin/theme listing makes it slow or heavy, or how it behaves on a multi-site setup. It also does not contradict the annotations.

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 front-loaded sentence with the verb and resource first, followed by the field list. The enumeration is long but each item earns its place because there is no output schema to carry that information; only minor trimming would be possible.

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 carries the burden of telling the agent what comes back, and it does so explicitly (name, URL, description, version, theme, timezone, language, plugins, themes). The single optional parameter is documented in the schema, and annotations cover the safety profile. The only gap is lack of guidance on how this differs from overlapping siblings like wp_site_health or wp_get_settings.

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?

There is one parameter with 100% schema description coverage, so the schema already explains that site_id targets a specific site and is optional when only one site is connected. The description adds no additional detail about multi-site targeting or what happens if the ID is invalid, so the baseline of 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?

Specific verb (Get) plus resource (WordPress site information) with an explicit enumeration of the returned fields, so an agent knows exactly what comes back. It does not, however, distinguish itself from similarly named siblings such as wp_get_settings, wp_site_health, wp_list_plugins, or wp_list_themes, whose scopes partially overlap (listing plugins/themes).

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?

Usage is only implied: 'get WordPress site information' is self-evidently a discovery/overview call, and it reads naturally as a first step before other wp_* tools. There is no explicit when-to-use guidance and no statement of when to prefer wp_get_settings, wp_site_health, or the dedicated wp_list_plugins/wp_list_themes tools that cover a subset of the same data.

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