Upload image or video

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

With no annotations, the description carries the full behavioral burden; it does disclose the return value ('Returns the blob id') and that base64 is accepted alongside file paths, which is useful. It omits permissions/auth requirements, size limits, and what happens on re-upload or failure — meaningful gaps for a mutation tool.

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?

Three short sentences, each earning its place: action, category routing, and return value. Front-loaded with the verb and resource.

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?

No output schema exists, and the description compensates by naming the return value (blob id). Parameter behavior is largely covered by the schema plus the category routing. Minor gap: no guidance on choosing filePath vs base64Data beyond 'alternative'.

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 75%, so the schema documents most fields, but the description adds real meaning by mapping each enum value to its domain (billboard-* for deals, post-* for chirps) and by noting base64Data is an alternative to filePath. That goes beyond the raw enum list.

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+resource ('Upload a local image/video file ... to BillboardBug') with both input modes named. It also clarifies where each category lands (deals vs chirps), so an agent can place it relative to create_deal/create_chirp without opening other schemas.

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?

Explicitly tells the agent which category to use for deals versus chirps, which is the primary selection decision for this tool. It stops short of saying when to call upload_media at all (e.g., before create_deal vs. using generate_image as an alternative), but the context is clear.

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