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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is covered structurally. The description reinforces this with 'Free: changes nothing and makes no picture' and adds a workflow constraint (approval gate before soclo_image_upscale) that annotations cannot express. It stops short of saying what the returned pricingVersion is used for or how long the quote stays valid.

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?

Two sentences with no filler, and the core purpose plus the key free/no-op fact are front-loaded. The fragment 'Free: changes nothing and makes no picture' is slightly awkward phrasing, but it is compact and information-dense.

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 quoting tool, the description covers purpose, cost implications and the required approval handoff. The one remaining gap is what the response contains beyond price and pricingVersion, and what the agent should do with pricingVersion when finally calling soclo_image_upscale.

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 and there is nothing the description could add on that axis. The mention of 'current account' usefully signals that pricing is derived from the active account rather than passed in.

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 names a specific verb and resource — 'Get the current account price and pricingVersion to upscale a photo' — which is unambiguous and clearly distinct from the mutating sibling soclo_image_upscale. An agent can tell instantly that this is the read-only quoting step of an upscale workflow.

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?

It gives explicit sequencing guidance: show the price, wait for approval, then call soclo_image_upscale. The 'Free: changes nothing and makes no picture' clause draws a sharp line between this tool and the paid sibling that actually produces output, so there is no ambiguity about which to invoke.

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