wordpress_update_media

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

The description claims to update 'alt text, caption, title,' but the input schema only includes a required 'mediaId' parameter—no fields for the claimed metadata. This mismatch misleads the agent about what data to provide. No annotations exist to clarify behavior, so the description must stand alone, but it contradicts the schema.

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, short sentence, which is concise but omits essential details about parameters and behavior. It is front-loaded with purpose but insufficient for an agent to use the tool correctly.

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 an update tool with no output schema and incomplete parameter specification, the description fails to provide enough context. The agent cannot determine the expected request body or the response format, making the tool difficult to invoke reliably.

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%, and the description adds no semantics for the sole parameter 'mediaId.' It mentions updateable fields (alt text, caption, title) that are not in the schema, creating ambiguity and likely causing incorrect tool invocation.

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 updates media file metadata, specifically alt text, caption, and title. This verb-resource pair is precise and distinguishes it from siblings like wordpress_get_media (read) or wordpress_upload_media (create).

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 tool versus alternatives, such as whether it is suitable for partial or full updates, or prerequisites like ensuring the media file exists. The sibling list includes many tools, but no comparative usage advice is provided.

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