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

The description discloses the crucial behavior that the transaction is unsigned and requires client-side signing, which is not captured in the annotations. This explains the zero-custody pattern and sets expectations for the return value. No contradiction with annotations.

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 three sentences, each contributing value: the action, the mission, and the usage pattern. No redundant 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?

For a simple two-parameter tool, the description covers the action, return behavior (unsigned transaction), and purpose. It doesn't detail the return format, but the absence of an output schema and the description's clarity about the unsigned transaction make it sufficiently complete.

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 schema already describes both parameters, but the description adds suggested donation amounts (0.01, 0.1, 1 SOL) which provide practical guidance for the amountSol parameter, going beyond schema constraints.

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 tool 'Build an unsigned SOL transfer to support Blueprint development', using a specific verb and resource. It distinguishes itself from sibling transaction builders by specifying the donation context and the unsigned/custody pattern.

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 description provides clear context for when to use this tool: when someone wants to donate to Blueprint. It references the 'same zero-custody pattern' as other transaction builders, implying segmentation from staking transaction tools, but doesn't explicitly name alternatives or exclusions.

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