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

Beyond the readOnly/idempotent annotations, the description explains why this tool exists: a render spends model credit and is gated behind a browser check that an automated client cannot pass. This is valuable behavioral context that the annotations alone do not convey.

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?

Three sentences, each earning its place: the first states the core output, the second gives the usage condition, and the third explains why automation cannot replace the link. The key information is front-loaded and there is no redundant filler.

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 a single optional parameter, annotations covering safety, and a clear description of the returned URL and its purpose, nothing essential is missing. The description also anticipates the likely failure mode—an agent trying to perform the edit itself—and addresses it directly.

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 input schema already documents the only parameter, task, with a clear description and enum values, giving 100% schema coverage. The tool description adds high-level context about the edit workflow but does not need to explain parameter semantics further because the schema already does so.

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 specific verb and resource: 'Returns the URL a person should open to upload listing photos and run an edit themselves.' It clearly distinguishes this from actually performing the edit, which is the core purpose of the tool. This prevents an agent from confusing it with editing-capable or checkout-related siblings.

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 explicitly says 'Use this when someone wants an edit performed' and explains that editing is deliberately not callable over MCP. It also instructs the agent to 'Hand the person the link rather than attempting the edit,' providing both when-to-use and when-not-to-attempt guidance.

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