Site settings

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

Annotations are absent, so the description bears the full burden. It identifies the REST endpoint (wp/v2/settings) and the fields returned, which implies a read operation. However, it never explicitly states that this tool is non-mutating or what response shape to expect; for a simple zero-parameter GET this is a minor gap.

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, well-formed sentence that front-loads the resource and then gives concrete examples of the settings included. There is no filler or repetition.

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 zero-parameter read tool, the description is largely sufficient: it names the endpoint and the contents. The only omission is an explicit statement of the return type, but with no output schema and a well-known REST resource, this is easy for an agent to infer.

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 takes zero parameters, so the input schema is complete at 100% coverage. The description adds no parameter details, but none are needed; baseline 4 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?

The description names the target resource (wp/v2/settings) and lists the specific fields it exposes (site title, tagline, timezone, language, front page). The verb is only implied by the tool name and REST endpoint, and it doesn't explicitly distinguish from wp_update_settings within the text, so it falls just short of a 5.

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?

There is no guidance about when to call this tool instead of alternatives. It neither states that it is the read counterpart to wp_update_settings nor notes any conditions or prerequisites. The only usage signal is the get naming convention.

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