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

Annotations already declare readOnlyHint=false and destructiveHint=false, so the mutation/safety profile is partly covered. The description adds that the bond is posted on-chain but omits permissions/token-approval prerequisites, whether the bond is refundable or slashable, and gas considerations — meaningful gaps for a value-transfer operation.

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 and the requirement, with no filler. Every sentence carries distinct information (action, condition, return value).

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?

It helpfully states the return value (transaction hash) even though no output schema exists, and the annotations cover the safety profile. Still, for an on-chain mutation tool it leaves out prerequisites and bond lifecycle behavior, leaving the agent incompletely briefed.

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%, so both parameters (address, milestoneIndex) are already documented in the schema. The description adds no format, range, or 0-based indexing detail beyond what the schema already provides, so the baseline of 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?

States a specific verb (Deposit) and resource (operator bond for a milestone) and specifies it happens on-chain. It does not, however, distinguish itself from nearby siblings such as fund_escrow, which an agent might reasonably confuse with it.

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?

Gives a concrete usage condition: 'Required for Assurance Tier 3 jobs.' This tells the agent when the call is mandatory, but it names no alternatives and offers no when-not guidance, so it stops short of full routing clarity.

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