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

Annotations already declare the destructive/non-idempotent/open-world profile, so the description is not carrying that burden alone. It adds real value beyond them: the CREW_LAUNCHER_KEY-then-CREW_OPS_KEY credential fallback and the OnlinePumpSdk builder preference that avoids the CreatorFeesNotSwept failure. What it omits is any statement about irreversibility of the fee transfer, which matters given destructiveHint=true.

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?

Three tight sentences, front-loaded with the action, then credentials, then the failure mode being avoided. Dense and free of filler, though parenthetical program names and SDK jargon slightly interrupt the flow.

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 destructive, non-idempotent write with no output schema, the description covers mechanism, credential resolution and a known on-chain failure mode. Remaining gaps (return shape, retry/irreversibility semantics) are modest against annotations that already flag destructiveness and non-idempotency.

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 100%, including the mint pattern/example and the FORBIDDEN markers on secretKey/privateKey/launcherKey, so the schema does the heavy lifting. The description only indirectly reinforces the key handling ("uses CREW_LAUNCHER_KEY if set") without adding format or syntax detail, matching the baseline 3.

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 ("Distribute accrued creator fees") and names the underlying instructions (sweep + distributeCreatorFeesV2), so an agent knows exactly what on-chain action occurs. However, it never contrasts itself with the neighbouring crew_wire_fees tool, which is the closest potential alternative for fee movement.

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?

"Permissionless on-chain" tells the agent anyone may call it, and the key-selection sentence gives invocation context. But there is no explicit when-to-use vs when-not guidance, and the sibling crew_wire_fees (also fee-related) is not mentioned as an alternative.

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