wordpress_set_featured_image

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

No annotations are provided, so the description bears full responsibility for behavioral disclosure. It only says 'Set featured image' and does not reveal whether an existing image is replaced, what happens if the post or media does not exist, or any side effects. The mutation is implied but not elaborated.

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 a single sentence with no unnecessary words, immediately front-loading the action and subject. It is appropriately terse for a straightforward tool with two parameters.

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, but the absence of output schema and annotations means the description should explain more about the operation's behavior, such as requirements or error conditions. The current text is minimal and leaves critical context unanswered, making it incomplete for an agent to use confidently.

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% description coverage and the description mentions neither postId nor mediaId. The parameter names are self-explanatory to a human, but the description adds no clarification about which parameter maps to which field (e.g., postId vs mediaId) or any constraints 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 uses a specific verb 'Set' with a clear resource 'featured image (thumbnail)' and target 'post', making it unambiguous. It distinguishes this tool from other set_* tools (e.g., set_og_tags, set_seo_meta) by naming a unique resource, and the scope is clear.

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 gives no guidance on when to use this tool versus alternatives, nor does it mention any prerequisites (e.g., media must be uploaded first) or situations where another tool would be more appropriate. It is purely a one-sentence action statement.

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