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

Annotations only give readOnlyHint=false and destructiveHint=false, so the description usefully adds on-chain execution, built-in fee collection/registry tracking, and the PCC_GATEWAY_PRIVATE_KEY auth requirement. It does not disclose what is deployed/returned (e.g., escrow address) or reversibility.

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 short sentences, front-loaded with the action, then the value proposition, then the prerequisite. Nothing is redundant and every sentence 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 write tool with no output schema, the description covers purpose, mechanism, built-in behavior, and auth needs. It omits what a caller gets back (e.g., deployed escrow address/ID) and any link to follow-up tools like fund_escrow, leaving a small gap.

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% and all four required parameters (payer, arbiter, token, cwmId) are documented there, so the baseline is 3. The description adds no parameter-level detail such as token/arbiter constraints or cwmId usage.

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+resource (create a MilestoneEscrow contract) and the mechanism (PCCProtocol factory, on-chain). It is clearly distinguishable from read-side siblings like get_escrow or list_escrows, though it does not explicitly name a competing creation path.

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?

Implies when to use it: 'Protocol-deployed escrows have fee collection and registry tracking built in' signals choosing this over a plain/bare escrow when those features matter, and it names the required write credential. No explicit alternative or when-not condition is given, so it falls short of a 5.

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