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

Annotations only declare readOnlyHint=false, idempotentHint=true and destructiveHint=false; the description goes well beyond them with the free/no-purchase guarantee, the 202 preparing state and polling with identical inputs, the consentRequired one-tap flow, and the fact that consent is persisted once per account. These are exactly the behavioral facts an agent cannot infer from structured fields.

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 purpose and the brand-asset exclusion are front-loaded, and each subsequent sentence carries distinct operational content (polling, consent, pricing boundary). It is dense and slightly run-on, packing several separate instructions into single sentences, which costs a little readability.

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?

No output schema exists, yet the description names the fields that matter for the next step (exact preview, consentRequired) and explains the 202 polling contract. Combined with the pricing boundary and the hand-off to confirm and generate, an agent has everything needed to call and follow up correctly.

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?

Schema description coverage is 100%, so the schema already documents both sourceUrl and clientRequestId, including that the UUID is stable across preparing polls. The description largely restates that ('Pass the owned sourceUrl and a stable clientRequestId') without adding format or validation detail beyond the ownership-check note, so baseline 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?

States a specific verb and resource ('Free owner review of ONE ordinary Library image (kind=image) or one-off upload') with scope limits (ONE, ordinary vs. brand asset). It names the sibling that handles the excluded case (soclo_brand_photo_reference), so an agent can route without opening either schema.

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 when-to-use (ordinary Library image or one-off upload), when-not (kind=brand_asset), and the follow-on tools (soclo_photo_reference_confirm for consent, soclo_image_generate after price approval). It also states the prerequisite that the URL must be the exact current owned URL because Soclo verifies ownership.

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