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

With no annotations, the description adds some behavioral detail (the builder parses amount against decimals). However, it omits key traits like side effects (none, since unsigned) and prerequisites (e.g., mint must exist). The contradiction with the schema's parameter description reduces trust.

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 very short and to the point, with no filler. It could benefit from a second sentence about return value, but it remains efficient for its length.

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 lacks critical context: it does not specify that the tool returns an unsigned transaction (important for a build tool), nor does it mention the need for subsequent execution. Given no output schema, this omission hampers an agent's ability to chain calls correctly.

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 claims 'amount' is a whole-token decimal string that the builder parses, but the schema states it is in base units (user multiplies by 10^decimals). This contradiction misleads the agent; the description adds no useful meaning and conflicts with the schema.

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 it builds an unsigned mint transaction, implying a build step. However, it does not differentiate from siblings like 'solknife_mint_supply_execute' or 'solknife_mint_supply_read', which could cause confusion for an AI agent.

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 no explicit guidance on when to use this tool versus its siblings (e.g., after building, use execute). The word 'unsigned' hints at a build-execute pattern, but no direct alternatives are mentioned.

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