wordpress_upload_media_from_url

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

Without annotations, the description discloses SSRF protection, MIME sniffing, and raw-binary POST, adding some behavioral context. However, it lacks details on failure modes, authentication requirements, or rate limits.

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 that is concise and front-loaded with the action. The '[UNIFIED]' prefix is extraneous but does not detract significantly. Every word earns its place.

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 a tool with 10 parameters and no output schema or annotations, the description is insufficient. Key parameters like convert_to, set_featured, and attach_to_post are undocumented, leaving agents unable to use them correctly.

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 the description does not explain any of the 10 parameters beyond their implicit names. No parameter behavior or format is clarified, leaving significant ambiguity.

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 uploads media from a public URL to WordPress via sideloading. It mentions SSRF protection, MIME sniffing, and raw-binary POST, which distinguishes it from sibling tools like wordpress_upload_media_from_base64 and chunked variants.

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 implies use for remote URLs (sideload) but does not explicitly state when to use this tool versus alternatives (e.g., from_base64, chunked). No exclusions or context for selection are provided.

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