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

Annotations declare the mutation profile (readOnlyHint=false, destructiveHint=true), but the description adds what annotations cannot: that it SPENDS credits, that spending is gated on owner approval, that image-edit permission is one tap per account, that people in photos are allowed, and that exact replays do not double-charge.

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?

Front-loaded with the action, then the quote/approve/spend constraints, then recovery and scope. Every sentence carries information, though several are dense run-ons and the block runs long enough that a reader must parse carefully.

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 costly, non-idempotent, open-world mutation with no output schema, the description covers the prerequisite quote, the spend gate, the permission requirement, retry/replay semantics, the recovery path, and even names the returned libraryAssetId and resultUrl.

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 coverage is 100%, so the baseline is 3, but the description adds relational meaning: the credit fields must come from the approved quote, ownerApprovedPrice must be true, zero is only valid when the account quote permits, imageUrls come from soclo_photo_reference_prepare or soclo_brand_photo_reference in original order, and the UUID must be saved before calling.

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 with scope: 'Remove the background from one reviewed photo.' The scope word 'one' and 'reviewed' distinguish it from the sibling quote tool, and the closing 'This tool does not publish' bounds the outcome.

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?

Explicit sequencing: quote first with soclo_image_remove_background_quote, spend only after owner approval, and use soclo_image_recover with the original clientRequestId after a lost result or unknown charge, with a hard exclusion ('never start a replacement purchase').

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