Get a photo upload link for your owner

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

Annotations declare the mutation/safety profile (readOnlyHint=false, destructiveHint=false, openWorldHint=false), and the description adds real behavior beyond that: the link expires in 60 minutes, uploads land at full quality, and GLONGUS_API_KEY is required. It leaves out whether the link is single-use or can be revoked/regenerated, so not quite a 5.

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 core value ('The best way to add photos') followed by the returned artifact, the usage rule, and the follow-up in two tight sentences. No filler or redundant restatement of the title.

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?

With one fully-documented parameter, a clear safety annotation set, and no output schema, the description covers everything an agent needs: what it returns (a link), how long it lives, who consumes it, the auth requirement, and the next tool to 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 coverage is 100% and the single parameter listing_id is fully documented in the schema (including the ^lst_ pattern). The description only implies it targets 'one of your listings' and adds no format or edge-case detail beyond the schema, so baseline 3 applies.

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 (returns a photo upload link) plus its scope: an owner-facing link for one listing at full quality. It implicitly distinguishes itself from add_listing_photo by warning 'never re-type an image as base64', so an agent can pick the right sibling without opening a schema.

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: 'Use this whenever the photo is with your owner or only visible to you in the chat', with an explicit when-not alternative (don't base64 an image). It also gives the follow-through step: send the link, then check photos with get_listing.

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