wordpress_upload_media_from_base64

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

No annotations are provided, so the description must disclose behavioral traits. It only states the basic action of uploading, lacking details about side effects, permissions, idempotency, error handling, or return values. For a mutation tool with 11 parameters, this is insufficient.

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 key purpose and usage guidance. However, given the tool's complexity, the conciseness sacrifices necessary detail for parameter semantics and behavior.

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?

Despite 11 parameters and no output schema or annotations, the description does not cover return values, error conditions, prerequisites, or the processing of base64 data. It is insufficient for an agent to use the tool 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 only mentions 'base64-encoded data' and 'filename', ignoring the other 8 parameters (mime, title, caption, alt_text, convert_to, set_featured, skip_optimize, attach_to_post). This fails to provide meaningful guidance 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 clearly states the verb 'Upload' and resource 'base64-encoded file to WordPress media library', and distinguishes from a sibling (upload_media_from_url) by specifying small file size (<10 MB) and chat-attached use case. However, it does not differentiate from chunked upload siblings.

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?

Explicitly states when to use this tool (for chat-attached images/files <10 MB) and when not (for larger files), with an explicit alternative mentioned (upload_media_from_url) and a note about chunked path later.

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