gbp_upload_media

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

With no annotations, the description carries the full burden of behavioral disclosure, but it only states the basic action. It does not mention side effects, authentication requirements, upload constraints, whether media is fetched from sourceUrl, or how the API processes the upload.

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 direct sentence that front-loads the essential purpose without wasted words. It is as concise as possible for the basic action it names.

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?

For a tool with nested parameters, no annotations, and no output schema, the description is too thin. An agent would not know how to construct mediaItem correctly, whether sourceUrl is required for upload, or what happens after the call.

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 50%, and the description adds little beyond what the schema already shows. It clarifies that 'parent' is a location and 'mediaFormat' can be PHOTO or VIDEO, but it does not explain the nested mediaItem fields such as sourceUrl, category, or description.

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 states a specific verb ('Uploads'), a concrete resource ('GBP location'), and the object being uploaded ('a photo or video'). This clearly distinguishes the tool from siblings like gbp_list_media or gbp_create_post.

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?

No guidance is provided about when to use this tool versus alternatives such as gbp_create_post or gbp_list_media. There are no conditions, prerequisites, or exclusions stated.

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