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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint=false, and destructiveHint=false, so the safety profile is covered. The description adds that the response is a recommendation covering proof gates, AI-audit enablement, and example parameters, but says nothing about freshness, caching, or failure behavior. With an output schema present, this is adequate rather than rich.

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?

Two sentences plus an example list; the first sentence front-loads the purpose and the returned payload. The example list is somewhat long but directly improves parameter interpretation, so it largely earns its place.

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 one-parameter, read-only lookup with an output schema and complete safety annotations, the description covers purpose and likely inputs well enough for an agent to call it. The only material gap is workflow ordering relative to escrow setup tools, which is left implicit.

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?

The single job_type parameter has 0% schema description coverage, so the description must carry its meaning. It does so with nine concrete example values spanning gig tickets, software development, domain verification, NFT art, invoice payment, and more, though it does not say whether the field is free-form or must match a controlled vocabulary.

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: returns recommended escrow release conditions, and enumerates the output categories (proof gates, AI audit, example parameters). It is distinguishable from action-oriented siblings such as prepare_escrow or request_escrow because it only recommends configuration, though it does not name those alternatives.

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 phrase 'Given a job or deliverable type' supplies an input context, but the description never states when to call this tool versus prepare_escrow, request_escrow, or assess_counterparty_and_job, nor whether it should precede escrow setup. Usage is implied rather than instructed.

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