wordpress_set_custom_meta

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

No annotations provided, so description must carry full burden. It states 'Set' indicating mutation but lacks details on overwrite behavior, authentication, required capabilities, or error handling. Minimal transparency for a write operation.

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?

Extremely concise at one sentence, but underspecified. While no wasted words, the brevity sacrifices informativeness. Structure is flat; lacks front-loading of critical details.

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 simple set tool with no output schema, the description fails to mention return value (e.g., success/failure, updated meta value), behavior on existing keys, or typical use cases. Incomplete given the tool's simplicity and lack of structured documentation.

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 0%, yet the description adds no explanation of the three parameters (postId, metaKey, metaValue). Schema types are given but no semantic meaning; the description does not clarify what each parameter represents or its format.

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?

Description clearly states it sets custom post metadata fields, distinguishing it from general site options or featured images. However, it doesn't explicitly differentiate from other 'set' tools like wordpress_set_seo_meta, but the mention of 'custom fields and plugins' hints at its generic nature.

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?

No guidance on when to use this vs alternatives. The phrase 'useful for custom fields and plugins' implies context but doesn't exclude when not to use it (e.g., when only a specific meta key is needed). No prerequisites or alternative tool suggestions.

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