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

The description adds some behavioral context: it states that private keys are not exposed to the server, and it warns that this is experimental and test-only. These are not present in the annotations, which already indicate destructiveHint=true and readOnlyHint=false. However, the description doesn't disclose what side effects occur, such as on-chain transactions or state changes. Given the annotations cover the destructive nature, the description adds a bit but not enough for a higher score.

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 brief and front-loaded with the core purpose. It includes a string of disclaimers in all caps, which are repetitive but not excessively long. The structure is acceptable, though the disclaimers could be condensed. Overall, it's concise and to the point.

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?

This is a complex tool with nested objects and 5 parameters, yet the description only gives a high-level purpose and warnings. There is no output schema, and the description does not explain the meaning of commitment, signature, bond, or publish. An agent would lack critical information about how to construct the parameters, what constitutes a valid commitment, or what the tool returns. This is severely incomplete for such a complex operation.

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 description provides zero information about the parameters (commitment, signature, bond, publish, mode). It only implicitly references the mode via 'sign or bond'. With schema description coverage at 0%, the description does not compensate for the lack of parameter documentation. An agent would have to infer meaning from the schema alone, which is insufficient for a tool with this complexity.

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 clearly states the action: 'Sign or bond a test-network purchase commitment'. It specifies the resource (purchase commitment) and the two modes (sign or bond). It also differentiates from siblings by focusing on commitment creation, which is distinct from other tools like caravan_attest or caravan_check_pools. However, it doesn't explicitly name alternatives, so it's not a perfect 5.

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?

There is no guidance on when to use this tool versus siblings. The description only includes disclaimers about test network, but doesn't explain the conditions under which one should sign versus bond, or when to choose this tool over others. No alternatives are mentioned.

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