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

With no annotations and no behavioral detail, the description does not disclose who can open a dispute, what happens after opening one, whether it is reversible, or what permissions are required. For a likely mutation operation on an escrow, this is a complete absence of behavioral context.

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 description is extremely terse, a single phrase plus a domain tag. While concise, it is under-specified for a mutation tool with a required reason and optional nested evidence, so the brevity does not earn its place as useful guidance.

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?

Given no annotations, no output schema, 0% schema description coverage, and three parameters including a nested evidence object, the description is far too thin to be complete. An agent lacks the context needed to invoke this tool correctly.

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 0%, so the description must carry all parameter meaning, but it adds nothing about escrow_id, reason, or the nested evidence object. An agent cannot tell from the description what a valid reason looks like or what evidence should contain.

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 clear action and resource: opening an escrow dispute. The [defi] tag gives domain context, but it does not differentiate from sibling tools such as escrow_create or escrow_release beyond the verb 'dispute'.

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?

No guidance is provided on when to use this tool versus alternatives like escrow_release or escrow_create, nor are prerequisites or conditions for opening a dispute stated. The description implies a scenario but leaves selection entirely to inference.

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