wordpress_set_custom_meta

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

No annotations are provided, so the description carries full burden. It states 'Set' (implying a write/mutation), but doesn't disclose behavioral traits like required permissions, whether it overwrites existing values, error handling, or side effects. The mention of 'useful for custom fields and plugins' adds minimal context but lacks critical operational details.

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 brief and front-loaded with the core action. Both sentences are relevant, though the second adds limited value. It avoids redundancy and is appropriately sized for a simple tool.

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?

Given the tool's complexity (a mutation with 3 parameters), no annotations, no output schema, and 0% schema coverage, the description is inadequate. It lacks details on behavior, parameters, error cases, and output, making it incomplete for safe and effective use by an AI agent.

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%, so the schema provides no parameter details. The description does not explain what 'postId', 'metaKey', or 'metaValue' represent, their formats, or examples. It fails to compensate for the lack of schema documentation, leaving parameters largely unexplained.

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 ('Set') and resource ('custom post metadata field'), making the purpose understandable. It distinguishes from obvious siblings like 'wordpress_update_post' by focusing on metadata, though it doesn't explicitly differentiate from all potential metadata-related tools.

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 versus alternatives (e.g., 'wordpress_update_post' for core fields, or other metadata tools if they exist). It mentions it's 'useful for custom fields and plugins,' which implies a context but doesn't specify prerequisites, constraints, or clear alternatives.

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