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

Beyond the annotations (destructiveHint=true, readOnlyHint=false), the description discloses that the tool returns an unsigned transaction requiring local signing, that only the original client wallet passes the on-chain check, and that the verification timeout remains anchored on submitted_at so approval cannot freeze escrow. These are non-obvious behavioral traits that materially affect invocation.

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?

The description is moderately sized but every sentence earns its place: purpose, return behavior, wallet constraint, timeout nuance, and a pointer to the list tool. The unusual prefix '[STATE: controls escrow outcome] (CLIENT)' is slightly cryptic but not padding; overall it is well-structured and front-loaded with the main action.

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?

Given there is no output schema, the description clearly states the return value (unsigned tx), the required follow-up (submit_tx), the permission constraint (original client wallet), and the source for valid task_ids. This covers everything an agent needs to correctly invoke the tool and interpret its result.

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 coverage is 100%, so the input schema already fully documents both `network` and `task_id` (including the format). The description adds only a pointer that task_ids come from shillbot_list_pending_approval, which is minor context. Baseline 3 is appropriate because the schema does the heavy lifting.

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 specific verb ('Approve'), a resource ('agent-submitted content'), and the actor ('task you funded'), making the tool's job immediately clear. It also distinguishes itself from siblings by referencing the follow-up action (shillbot_submit_tx) and the listing tool (shillbot_list_pending_approval), so an agent can tell this apart from claim/complete/finalize without opening schemas.

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 gives clear context: use it to approve pending items, find them via shillbot_list_pending_approval, and then submit the returned tx via shillbot_submit_tx. It does not explicitly state exclusions (when not to use), but the tool's role is distinct and the workflow is well-anchored, so guidance is strong rather than vague.

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