get_media_upload_instructions

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

With no annotations, the description carries the behavioral burden. The word 'Get' and the phrase 'upload token and S3 post parameters' make clear this is a retrieval of upload instructions rather than an upload or mutation. It stops short of noting expiration or permission requirements, but those are not required for invocation.

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 two short lines with no filler. The primary purpose is front-loaded, and the type values are attached as a compact, scannable parameter note.

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 tool is simple, has one optional parameter, and has an output schema, so the description does not need to explain return values. It covers purpose, operating context, and the parameter's allowed values. Minor missing detail such as the upload flow after obtaining the token is not critical for tool selection.

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 schema only defines a 'type' string with a default. The description compensates by enumerating the acceptable values ('image-event-logo', 'image-event-description'), which is the main semantic information an agent needs. It does not explicitly explain the difference between the two values, but their names are self-explanatory.

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 opens with a specific verb ('Get') and resource ('upload token and S3 post parameters') and states the end goal ('uploading an image to Eventbrite'). It is immediately distinguishable from siblings like get_media because it concerns upload instructions rather than media retrieval.

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?

It provides a clear context for use: an agent needing to upload an image should call this to obtain upload credentials. It does not name exclusions or alternative tools, but the tool set includes no other upload-instruction sibling, so the intended use is evident.

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