wordpress_update_settings

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

No annotations are provided, so the description carries full burden. It only states 'Update site settings' but does not disclose side effects, required permissions, or whether changes are reversible. The behavior is partially clear but insufficiently detailed.

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 highly concise with one sentence containing the verb and examples. It is front-loaded but could benefit from slightly more structure without losing brevity.

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 0 parameters, no output schema, and no annotations, the description barely covers the tool's purpose. It omits what happens when settings are updated, return values, and the scope of 'etc'. More detail is needed for a mutation tool of this significance.

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 input schema has 0 parameters (100% coverage trivially), yet the description mentions specific settings like 'title, description, timezone' that are not defined in the schema. This creates a contradiction and misleads the agent into expecting parameters that do not exist.

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 verb 'Update' and the resource 'site settings', with examples like 'title, description, timezone'. It distinguishes from read-only tools like wordpress_get_settings, but does not explicitly differentiate from other update tools such as wordpress_update_option, which might cause confusion.

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 no guidance on when to use this tool vs. alternatives like wordpress_update_option or wordpress_update_page. There is no mention of prerequisites or scenarios where this tool should be avoided.

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