wp_upload_media

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

No annotations are provided, so the description carries the full burden for behavioral disclosure. It mentions a two-step process (upload and set attachment metadata) but omits side effects, required permissions, reversibility, or any mention of the dry_run parameter's preview behavior. An agent cannot infer what gets written or changed.

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 front-loads the verb and object, and every phrase contributes meaning. There is no filler, repetition, or tangential information.

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?

With 9 parameters, no annotations, and no output schema, a description that only states the core action is insufficient. It lacks usage guidance, parameter semantics, and behavioral side effects, so an agent would need to investigate the schema and sibling tools to call it 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 description coverage is only 11%, making the description responsible for compensating. It vaguely summarizes parameters as 'set attachment metadata' without naming title, caption, alt_text, description, post, filename, mime_type, or dry_run. The source types are already explicit in the schema, so the description adds little beyond what the schema already shows.

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?

Description uses a specific verb and resource ('Upload media') and adds source variants ('local path, URL, or base64 source') and a secondary action ('then set attachment metadata'). This clearly distinguishes it from sibling tools like wp_list_media, wp_get_media, wp_update_media, and wp_delete_media.

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 when to use the tool: whenever an agent needs to upload media from a local path, URL, or base64 source. However, it provides no explicit guidance about alternatives or exclusions, such as using wp_update_media for existing media or wp_set_featured_image for featured images.

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