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

No annotations are provided, so the description carries the full burden. It does add real behavioral context: new contracts carry declared access/IP constraints and an Ed25519-signed version, and revision requires an idempotency_key. However, for a multi-action mutation tool it omits auth requirements (agent_key), reversibility/irreversibility of fund vs create, and side effects of open.

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 five action verbs are front-loaded before the per-action endpoint details, and each action block is terse. It is dense but every line maps to a required action; the raw URL/HTTP-method notation is somewhat implementation-level boilerplate.

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 11 parameters, a oneOf schema, no annotations and no output schema, the description covers the primary create/read/fund/revision/open workflow adequately but leaves the auth model and several parameters (payment_signature, transfer_id, handle, delete_credential) unexplained. Adequate but with clear gaps for a tool of this complexity.

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 only 9% and the body schema is a generic object pointing back to this description, so the described body fields (brief, data_access, ip_constraints, revises_id, amount_usd, request) genuinely compensate. Still, agent_key, wanted_id, transfer_id, handle, delete_credential, payment_signature and id are documented in neither place.

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?

The description names a specific resource (supplier checkout contract) and enumerates the five distinct operations it can perform (create, read, revision, fund, open), each with its HTTP endpoint. An agent can tell exactly what this tool does without opening the schema.

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?

It implicitly tells the agent which action to pick via the per-action body/endpoint breakdown, but never states when to use this tool at all rather than siblings such as supplier_payout or procurement_contract_run, nor any prerequisites or when-not-to-use conditions.

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