Get upload URLs for Untappd check-in photos

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

Annotations declare readOnlyHint=true, and the description reinforces this with 'Posts nothing to Untappd', so there is no contradiction. Beyond annotations it adds operationally critical facts: 30-minute URL expiry, 15 MB cap, JPEG/PNG only, the requirement to send exactly the returned Content-Type, and the deployment dependency on a blob store.

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?

Front-loaded with the purpose, then constraints, then the downstream handoff and the fallback. Dense but nearly every clause carries information; the parenthetical curl/Content-Type detail is slightly crowded but operationally necessary.

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, yet the description explains what is returned (blobKey plus a ready curl command) and how to consume it. Combined with expiry, format, and deployment constraints, an agent has everything needed to call it and chain into untappd_checkin.

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 100%, so the baseline is 3. The description still adds value beyond the schema by stating the 15 MB size limit and by explaining what the returned blobKey is used for downstream, which the schema cannot convey.

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?

Specific verb plus resource: 'Get signed upload URLs for check-in photos', scoped to the HOSTED connector. It immediately separates itself from untappd_checkin by naming the downstream handoff (photo_blob_key) rather than duplicating the check-in action.

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?

Explicit when-to-use: only on the hosted connector, which cannot read local files. Explicit alternatives for the other case: 'on a local install use photo_path or photo_inline'. It also states the exact next step (run the curl, then pass blobKey to untappd_checkin).

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