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

Annotations already declare destructiveHint=true and readOnlyHint=false, and the description adds that only owners and admins may approve/reject and that archives are handled elsewhere. It does not explain the consequences of approve/reject, whether reject deletes or archives, or how idempotency applies, which are notable gaps for a destructive review tool.

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?

Two short sentences, front-loaded with the core list/approve/reject workflow and a useful boundary about archives. There is no filler.

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 an 8-parameter destructive tool with 0% schema description coverage and no output schema, the description is too thin. It covers the basic review workflow and role restriction but leaves required parameters, pagination, revision selection, reason usage, and return behavior undocumented.

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% across 8 parameters, so the description must carry parameter meaning, but it only loosely maps to the action enum ('list', 'approve', 'reject'). It says nothing about workspace, scope, limit, cursor, reason, revision, or idempotency_key beyond what the bare schema names imply.

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 clear review workflow: list pending Soul revisions and let owners/admins approve or reject them, with archives handled elsewhere. This distinguishes it from brand_memory_read and brand_memory_write, though the term 'Soul revisions' is not defined and no sibling is named explicitly.

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 signals when to use the tool (reviewing pending revisions) and gives an exclusion (archive approvals happen in AlphaWeb). It does not explicitly say when to use brand_memory_read or brand_memory_write instead, but the review/approval context is clear.

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