wordpress_get_settings

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

With no annotations provided, the description must convey behavioral transparency but only says 'Get', implying a read operation without detailing what settings are returned, whether any are excluded, or the response format. It does not disclose potential side effects or data scope beyond the vague 'site settings'.

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 extremely concise at six words, with no wasted text. However, it is so terse that it sacrifices informational value, keeping it from a perfect score.

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?

The tool is simple (no params, no output schema), but the description lacks sufficient context. It does not clarify what 'site settings' includes in the WordPress context, how the response is structured, or how it relates to other getter tools. The one-liner is too thin for an agent to confidently invoke the tool and interpret results.

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 are zero parameters, and the schema has 100% coverage by default. The description is not required to explain parameter meaning, and it does not attempt to. This meets the baseline for no-parameter tools.

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 states a clear action ('Get') and a clear resource ('WordPress site settings'), making the tool's primary purpose understandable. However, it does not distinguish this from sibling tools like wordpress_get_site_info or wordpress_get_option, which could also return site-related information.

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 on when to use this tool versus alternatives such as wordpress_get_site_info or wordpress_get_option. The context signals show many sibling getter tools, but the description offers no exclusions, prerequisites, or typical use cases.

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