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

Annotations already declare readOnly, non-destructive, idempotent, non-open-world, so the safety profile is covered. The description adds real value by saying the tool opens nothing by itself and returns instructional steps instead of acting, but it never describes the shape or fidelity of those returned steps, which is the actual output an agent must act on.

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 core workflow is front-loaded and clear, but the trailing sentence "Midjourney's official API: Midjourney has no public API (checked 5 Nov 2026)" is awkwardly phrased and a dated verification stamp that does little work for tool selection. The middle clause mixes what the tool returns with what the agent must do next in one run-on sentence.

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 zero-parameter, no-output-schema meta tool the description covers purpose, non-action, and the follow-up browser workflow. It remains incomplete on two things an agent needs: how the specific creation is selected, and what the returned step list looks like or how to verify success afterward.

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 takes zero parameters, so the baseline is 4 per the schema-coverage rule and there is nothing for the description to disambiguate. The only semantic gap is that the description never explains how the target creation is determined in the absence of any input parameter.

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 ("Upscale creation") scoped to the user's own Midjourney account, and crucially discloses that it produces step-by-step instructions rather than performing the upscale. It does not distinguish itself from siblings like midjourney_vary_creation or midjourney_download_creation, nor does it explain how the target creation is identified with zero parameters.

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?

Gives explicit sequencing: call this to get the screens/buttons/fields, then execute with the cotlet_browser_* tools in the user's Midjourney Cloud Browser, and clarifies it opens nothing itself. It stops short of when-not guidance (e.g., when to prefer vary or extend instead) and does not state which creation is being upscaled or any prerequisites.

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