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

Annotations already declare destructiveHint=true, idempotentHint=false and readOnlyHint=false, so the irreversibility profile is covered. The description adds a genuinely useful behavioral fact (the bf_post_ manage key is required), but it does not warn that finalize/settle/rotate_key are irreversible or that rotating the key invalidates the existing one.

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?

A single front-loaded sentence with no filler; the ownership scope and auth requirement come before the action list. It is dense and slightly clause-heavy, but every clause carries information.

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 7-parameter destructive mutation with no output schema, the description covers auth and action semantics but leaves the payload parameters (allocations, settle fields) unexplained and says nothing about what a successful review returns. Adequate but with clear gaps.

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 29% schema coverage, the description usefully decodes the action enum (approve/reject/finalize/settle/rotate_key), which the schema leaves bare. However it says nothing about allocations, submissionId, settleBlock, or settleTxHash, so several parameters central to finalize and settle remain undocumented in both places.

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 (review) and resource (submission) plus the owner scope ('a mission you posted'), and enumerates the five concrete actions. It is clearly distinguishable from read-side siblings like get_submission_status and agent-side submit_work.

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?

The description establishes clear context for when to call it: reviewing work on a mission you posted, gated on holding the manage key. It maps actions to intent (approve a winner, reject a submission, finalize a split, settle, rotate key) but names no alternative tool or when-not condition.

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