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

The description discloses key behaviors: the link is valid for 24 hours, supports one or many files including a full carousel, and each file lands in the Post Bridge media library. Since annotations carry no read-only/destructive hints and the tool has no params, these details are valuable and accurate. No contradiction with annotations.

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?

Four sentences, each serving a distinct purpose: scope, behavior, follow-up workflow, and when-to-use. It is front-loaded with the core purpose and doesn't repeat the schema (which is empty).

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?

Given the empty input schema and absence of an output schema, the description fully covers what the agent needs: what the tool returns (24h link), how the user interacts with it, and the exact next steps (list_media then create_post) to complete a post. No missing information for correct invocation.

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?

The tool has zero parameters, so the schema already documents everything; with 0 params the baseline is 4. The description adds no parameter details, but the workflow guidance clarifies what the returned link is for.

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 ('Get an upload page') and the exact resource type (a temporary upload page/link for device-local files without a public URL). It distinguishes itself from upload_media by explicitly naming the condition ('no URL, or larger than 3MB'). No ambiguity about what the tool accomplishes.

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?

Explicitly states when to use: 'Use this whenever the user wants to post a file that upload_media cannot reach'. It also provides a step-by-step workflow (give link, wait for upload, call list_media, then create_post), leaving no doubt about how it fits with siblings.

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