Upload media

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

Annotations only indicate non-read-only and non-destructive, so the description carries the behavioral burden. It adds meaningful behavior: the file is stored in BulkPublish, supported formats are listed, max size is stated, and the url/filePath exclusivity is disclosed. It does not mention return values or side effects beyond storage, but no contradiction exists.

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?

Four sentences cover purpose, source, storage, formats, size, and parameter exclusion with no redundant wording. The most important usage guidance is front-loaded.

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?

The description covers input selection, constraints, storage destination, and intended use case. Since there is no output schema, it would benefit from explicitly stating what is returned (e.g., a media ID), but the current information is sufficient for most correct invocations.

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%, so parameters are already documented. The description adds value by clarifying that url and filePath are mutually exclusive and by providing supported format and size constraints that affect parameter usage.

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 names a specific verb ('upload') and resource ('media file'), and clearly scopes it to images/videos from a URL or local file path. It also states the storage destination (BulkPublish), which distinguishes it from read/list/delete media 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?

The description explicitly says to use this when the user provides an image/video to attach to a post, which gives clear invocation context. It does not explicitly name alternatives or exclusion conditions relative to sibling upload tools like create_media_upload, so it stops short of a 5.

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