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

With no annotations, the description carries the full burden and does disclose real behavior: funds route to the beneficiary on trigger, escrow returns to the insurer otherwise, and an on-chain settlement event is emitted. It omits authorization requirements (who may sign), irreversibility, and failure behavior for already-settled policies, which are the main risks for a mutation tool.

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 action and its two outcome branches are front-loaded in the first two sentences, with the event-emission note last. Slight redundancy between the description and the beneficiary schema text keeps it off a 5.

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 two-parameter mutation with an output schema already covering return values, the description gives enough payout mechanics to call it correctly. The remaining gaps are operational (caller authorization, re-settlement behavior) rather than structural.

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 schema already explains policy_id and the beneficiary pubkey, including that the beneficiary's token account receives coverage. The description restates the beneficiary's payout role without adding format or validation details beyond the schema, 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 and resource ('Trigger settlement of a parametric insurance policy') and even branches into the two possible outcomes. It does not, however, distinguish itself from the sibling mint_settle_cell, which an agent could plausibly confuse it with.

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 conditional branches ('if the policy was marked triggered... if the policy expired without a trigger') imply when this is the right call, but usage is only implied. There is no explicit statement of preconditions, who is permitted to call it, or when to prefer mint_settle_cell instead.

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