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

Annotations already cover readOnly/idempotent/non-destructive, but the description adds genuinely new facts: the read:brand permission scope and the concurrency (CAS) semantics, including that callers must persist the exact revision. 'Free; changes nothing' is redundant with readOnlyHint.

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?

Four short sentences, front-loaded on what is read and the key constraint (keep the revision). The 'Free; changes nothing' clause duplicates annotation information and is the one sentence that doesn't fully earn its place.

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?

With no output schema, the description does the necessary work of flagging that a revision is returned and when it can be null. The only gap is not distinguishing this read from the sibling brand-get-style reads, which leaves a small selection ambiguity.

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?

Zero parameters, so the baseline is 4; nothing in the schema needs explaining. The description correctly adds no parameter detail because there is none to add.

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?

Specific verb (read) plus resource (owner's Brand Kit) and the distinctive scope (returning the CAS revision alongside the kit). It doesn't mention the near-identical sibling soclo_brand_get, so an agent can't be fully sure which of the two to pick from this text alone.

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?

Clear workflow context: read this before calling soclo_brand_save, and carry the reported revision into expectedRevision. It notes the null-revision edge case. It stops short of naming soclo_brand_get or soclo_brand_status as alternatives, so the when-not is implicit.

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