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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so most of 'changes nothing' is restatement. The one genuinely additive claim is 'Free', which discloses the cost profile — a behavioral trait annotations do not carry. No detail is given on what the receipt contains or how a pending vs. failed state reads.

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?

One front-loaded sentence carries the operation, the kind mapping, the lookup keys and the recovery trigger, followed by a compact four-word safety/cost note. Nothing is padded and nothing is buried.

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 read-only lookup with no output schema, the agent still does not know what the receipt returns (status vocabulary, whether it includes the saved kit or scan results, what to do on not-found). The tool's calling contract is complete, but its interpretation contract is not.

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?

With only 33% schema description coverage, the description meaningfully compensates: it names targetId and the 'stable clientRequestId' and makes clear they are alternative/combined lookup keys ('and/or'), which explains why neither is in the required list. It does not explain the id semantics in depth (e.g., that clientRequestId should be the one supplied on the original save), so it stops just short of full coverage.

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 — reading the receipt of a Brand Kit save (kind brand_profile) or scan (kind brand_scan) — and explicitly frames it against the originating siblings soclo_brand_save and soclo_brand_scan. An agent can distinguish this from a status reader for other domains without opening the 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 a precise trigger: use it 'after an interrupted soclo_brand_save or soclo_brand_scan', which tells the agent the recovery context in which this tool applies. It does not address adjacent alternatives such as the generic soclo_ads_operation_status or soclo_brand_read for current state, so it stops short of full routing.

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