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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds real value beyond this: the exact capability required (`manage_options`, admin-only) and a full enumeration of returned fields, which lets the agent predict the response shape despite there being no output 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 the core action, then capability requirement, then return shape. The long field list is dense but earns its place because no output schema exists. Slightly list-heavy but no fluff.

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 enumerating return fields, and it discloses the auth capability. It leaves out pagination/edge cases but for a simple read-only settings fetch this is largely complete.

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 site_id parameter is fully documented with an enum and site label in the schema. The description adds nothing about the parameter, so baseline 3 is appropriate.

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: 'Retrieves the current WordPress site settings'. It distinguishes itself implicitly from setting-related siblings like wp_update_option or wp_get_option by its whole-site scope, though it doesn't name an alternative to steer against. Clear enough for an agent to identify the tool's job.

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 gives a prerequisite (requires `manage_options`, administrators only) but offers no explicit when-to-use versus alternatives guidance among the many site-info siblings (wp_get_site_info, core-get-site-info, wp_get_site_status). Usage is implied by the read nature of the tool, not stated.

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