wordpress_upload_media

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

No annotations are present, and the description merely says 'upload' without disclosing behavioral traits such as whether it overwrites existing files, authentication requirements, rate limits, or return value. Minimal transparency.

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?

A single sentence that is front-loaded with the purpose. No extraneous words, but could benefit from structured bullet points for requirements. Overall concise.

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 no output schema and no annotations, the description should mention what the tool returns (e.g., media ID, URL) and any constraints like file size or allowed types. It omits these, making it incomplete for a simple upload tool.

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 coverage is 0% and description adds meaning only for fileBase64 (base64 encoded) but not for filename. The filename parameter is required but its purpose and format are not explained. Lacks detail.

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 action (upload) and the resource (image or file to WordPress media library). It distinguishes from siblings like wordpress_get_media or wordpress_update_media, but does not provide additional context about file types or size limits.

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 mentions the need to provide base64 encoded file, but gives no guidance on when to use this tool versus alternatives (e.g., wordpress_set_featured_image or wordpress_create_post). No when-not or exclusion criteria.

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