Get WordPress Settings

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

Annotations already declare readOnly, idempotent, and non-destructive behavior. The description adds the admin capability requirement and specifies the return type (RawWpSettings object), providing useful behavioral context beyond 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?

The description is compact and front-loaded with the primary purpose. The note and Args/Returns sections are clearly structured with no unnecessary filler, making it easy to parse.

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 low-complexity read tool, the description covers the essential aspects: what it fetches, auth requirement, and return type. Pointing to wp_get_site_info for the field list is a helpful reference, though a bit indirect. It is complete enough for an agent to use effectively.

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 single parameter response_format is fully described in the input schema (markdown/json with human-readable vs machine-readable). The description repeats the default value but does not add significant new meaning beyond the schema.

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 'Fetch WP general settings' and enumerates specific settings like title, tagline, admin email, timezone, etc. This specific verb+resource combination distinguishes it from sibling tools such as wc_get_settings (WooCommerce) and wp_update_settings (mutator).

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 indicates a clear prerequisite (admin manage_options capability) and provides context on what settings are included. It does not explicitly mention when not to use it or point to alternatives, but the scope is clear enough for an agent to select it appropriately.

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