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

The description discloses that setting is required, that the address is stored as plaintext directory metadata, and that private keys are never seen. It also explains the clear-with-null behavior. Since annotations are all false and provide no safety profile, the description carries the burden and meets it well.

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 sentences, each adding meaningful context: the action, the metadata nature, the prerequisite, and the key-control warning. The essential action is front-loaded. 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 a simple two-parameter setter with no output schema, the description covers the purpose, the required precondition, the security consideration, and the clearing behavior. All necessary information to invoke correctly is present.

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?

The schema already documents both parameters fully (100% coverage), including the nullable address and the agent_key credential. The description adds minimal parameter-specific detail beyond re-stating the null behavior. Baseline 3 applies.

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 ('Set') and resource ('Base payout address for escrow releases/refunds'), and clarifies the clear-with-null behavior. This clearly distinguishes it from escrow lifecycle siblings like release_escrow and refund_escrow, which assume an address already exists.

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 explicitly states when the tool is required: before anyone can release a funded escrow to you, and before you can refund your own escrow. This gives the agent a clear condition for invoking it. It does not name alternatives, but no alternative exists for this configuration step.

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