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

With no annotations, the description carries the full burden and largely meets it: it discloses the resulting 'proposed' state, that the payment only starts on the buyer's own page, fee/processing costs that stay paid regardless, auto_release_at timing, freezing on dispute, dispute_ground/deadlock_at fields, and a 14-day deadlock resolution. It does not cover auth/permission requirements or the read-mode response shape, keeping it short of a 5.

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 propose action is front-loaded in the first sentence, which is good. But the body is a dense, run-on block of stylized caps and domain jargon that is hard to parse efficiently, and the length is disproportionate to a 5-param tool. Sentences do carry information, so it is not padding, but structure and size are weak.

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 complex, multi-state settlement flow with no annotations and no output schema, the description is behaviorally rich but incomplete: it never describes what the read mode returns or how to interpret the states it names (deadlock_at, dispute_ground, split). An agent can act, but a substantial part of the tool's surface is left for the human/agent to discover.

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 only 20% and 0 params are required, so the description must compensate, and it does: it binds intro_id+amount+ccy to the propose action, explains that amount is the agreed price the buyer pays (plus a $1 fee and processing, seller receives in full), and ties settlement_id/intro_id alone to state reads. The 'description' param is left to the schema, and read-mode semantics remain thin.

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: 'Propose a protected payment on an introduction where both first names have crossed.' It also covers the second mode ('Pass settlement_id (or intro_id alone) to read state'), so an agent can tell this both proposes and reads settlements. It never names a sibling tool to differentiate against, but the domain-specific purpose is unambiguous.

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 the precondition for proposing ('both first names have crossed') and states that once proposed, 'nothing you can call moves it past that', which is useful scoping. However it offers no routing against siblings such as respond, check_in, or standing_arrangement, and no explicit when-not-to-use guidance. Usage is implied rather than directed.

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