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

Annotations already establish readOnly, idempotent, and non-destructive behavior, so the safety profile is covered. The description adds genuine value by disclosing the conditional outcome and the return payload (media_url and preview link), which matters because there is no output schema. It does not say what is returned when nothing has been uploaded, which keeps it short of 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?

A single front-loaded sentence with no filler, communicating both the boolean outcome and the success payload. The sentence fragment style is slightly informal but costs no clarity.

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 one-parameter read tool with full schema coverage and read-only annotations, the description covers the essential question it answers and what comes back on success. The remaining gap is behavioral: no guidance on polling cadence or on the empty-result case.

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?

With one parameter at 100% schema description coverage, the schema fully documents upload_id and even its origin. The description adds no further semantics about the identifier or its format, so the baseline of 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?

The description states a concrete query over a specific resource: it reports whether a file was sent through an upload link and, if so, returns its media_url and preview link. The upload-link scoping distinguishes it from generic media or post tools, though it never names create_upload_link as its counterpart.

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?

The description gives no explicit when-to-use guidance, no mention of polling after create_upload_link, and no guidance on how to interpret the not-yet-uploaded case. The only workflow hint lives in the parameter schema ("upload_id from create_upload_link"), not in the description itself.

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