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

Goes well beyond the annotations (readOnly/destructive/openWorld/idempotent) by disclosing the gating model: every call is a spend-limited decision, unapproved payments are parked with ESCALATION_REQUIRED, and they execute only on retry with the same idempotency_key. It also states the credential never reaches the agent, covering the auth surface that annotations omit.

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?

Three dense sentences, front-loaded with the verb/resource and target URL, then the behavioral contract. Every sentence carries information, though the middle sentence packs gating, escalation, and idempotency into one clause chain.

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?

No output schema exists, so the description carries return-shape burden, and it does name the key terminal state (ESCALATION_REQUIRED) and the credential-handling behavior. It does not describe the general success/failure response shape or other error conditions, leaving a modest gap for a 7-parameter write tool.

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 86%, so the schema already documents parameters like idempotency_key, intent, and user_token. The description restates the idempotency_key retry semantics rather than adding new meaning, and says nothing about path, body, facts, or method beyond the method list already in the schema. Baseline 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 specific write verbs (create, change, pay) and the resource (the counterparty API reached through Regent) with the exact HTTP methods it proxies. It reads clearly as the write counterpart to counterparty_check_read, but it never names that sibling or explicitly draws the read/write boundary, so differentiation is inferred rather than stated.

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?

Usage is implied: write operations go through this tool and are gated under the agent's spend limit, with payments escalating to the owner. There is no explicit when-to-use/when-not guidance, no mention of when to prefer counterparty_check_read, pay, or budget_request_status, and no prerequisites stated for the caller.

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