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

Annotations already declare this is a non-read-only, open-world, non-idempotent write that is not destructive, so the safety profile is covered. The description adds that input is fetched from a URL and that a media ID and URL are returned, but it does not warn that repeat uploads create duplicates (relevant given idempotentHint=false) or state any permission requirements.

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?

Two tight sentences with the action front-loaded and the return-value payoff second. No filler, no redundancy.

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 no output schema, the description correctly compensates by naming the returned media ID and URL. For a low-complexity, three-parameter tool with full schema coverage this is close to sufficient, though duplicate-creation and permission behavior remain unstated.

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 100% and all three parameters are documented in the schema, so the baseline is 3. The description restates the URL source but adds no format, constraint, or multi-site behavior beyond what the schema already provides.

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?

States a specific verb (upload), resource (image/media library), and source (from a URL), making it immediately distinguishable from siblings like wp_list_media or stock_photo_search. An agent knows exactly what the tool does without opening the schema.

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 downstream use case ('can be used as featured images for posts or products') implies when the result is useful, but there is no explicit when-to-use guidance, no exclusions, and no mention of alternatives such as stock_photo_search or swiftly_request_upload. Usage must be inferred.

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