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

Beyond the annotations, it discloses that scan results are evidence rather than an automatic save, that website evidence uses a guarded scanner, that images are downscaled JPEG base64, and that credits are zero only within the free boundary. It also explains recovery behavior through clientRequestId and status polling, which is substantial operational context.

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 purpose and confirm behavior are front-loaded, and most sentences carry operational value. It is somewhat dense and jargon-heavy in the credit-boundary sentence, but the length is defensible for a tool with complex recovery and billing semantics.

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?

The description covers the key usage, safety, recovery, and cost context for a complex nested-schema tool. It is not fully complete because it does not explain several nested source fields or describe the scan result shape, and no output schema exists to fill that gap.

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 0%, so the description must carry parameter meaning. It explains confirm preview behavior and clientRequestId recovery semantics well, and it names website/photo/caption source types, but it leaves nested source fields such as currentBrand, platformStats, handle, captionsOrigin, and pastedCaptions unexplained.

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: scanning the owner's supplied website, photos, or captions with the app's free brand scan. It also distinguishes the tool from siblings by naming soclo_brand_save for saving and soclo_brand_status for recovery.

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 prerequisites (manage:brand and confirm:true) and explains that without confirm the call only previews. It also routes the agent to soclo_brand_save before saving inferred money-facing facts and to soclo_brand_status after interruption instead of repeating model work.

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