wp_get_site_info

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

With no annotations, the description carries full behavioral disclosure burden. It reveals that the tool combines two API endpoints (/wp-json/ root and /wp-json/wp/v2/settings), notes the settings endpoint is admin-only, and clarifies that admin email is returned only if accessible. This goes beyond basic read semantics and provides useful operational context.

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?

The description is three sentences, front-loaded with the core purpose, then adds implementation details. The list of fields is comprehensive but focused, and every sentence adds value. No filler or redundancy.

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-parameter, read-only tool with no output schema, the description is complete. It names the exact configuration values returned, explains the data source and access constraints, and notes version-specific behavior for the sitemap URL. Nothing critical is missing.

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 has zero parameters and schema coverage is 100%, so there is nothing to document. The description appropriately focuses on what is returned rather than inputs. Baseline 4 applies for tools with no parameters.

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?

The description clearly states the tool reads site-level configuration and enumerates specific fields (title, tagline, URL, etc.). It distinguishes itself from write operations like wp_update_site_settings and from wp_get_site_capabilities by focusing on configuration details.

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?

The description provides clear context for when to use the tool (reading site configuration), but it does not explicitly mention when not to use it or name alternatives. However, the sibling tools make the distinction obvious, and the read-only verb plus configuration scope is unambiguous.

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