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

The description discloses important side effects and constraints beyond the minimal annotations: 'persists a proposed agreement', 'may send the counterparty invite', response handoff block, and the production-only API key requirement. It also notes sandbox unavailability, which is critical for an agent deciding whether the call can succeed.

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?

Four dense sentences with no filler. Purpose, use conditions, side effects, and production configuration are front-loaded in a logical order. Every sentence adds actionable information.

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?

The description covers the tool's role in the lifecycle, side effects, response handoff, and environment requirements, which orients an agent well. However, given the schema is very complex, has no output schema, and zero parameter description coverage, the description could have explained the intended meaning of core required inputs and what the response handoff block contains.

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 compensate, but it only clarifies the type default and agent settlement rail. The five required parameters (parties, value, deliverable, terms, conditions) get no semantic explanation beyond their property names, leaving a large, nested schema largely unexplained.

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 uses a specific verb 'Create' with a precise resource ('production Spool (the agreement object)') and names the input ('from structured terms and acceptance criteria'). It also distinguishes the tool from siblings by explicitly excluding one-call unilateral verification, which orients the agent toward bilateral agreement lifecycle use.

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?

'Use when both parties will participate in the agreement lifecycle; do not use for one-call unilateral verification' gives clear when-to-use and when-not-to-use conditions. However, it does not name a specific alternative sibling tool, so an agent must infer that another tool (e.g., verify or propose) covers unilateral verification.

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