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

Annotations only cover readOnly/idempotent/destructive, but the description adds substantial context: the two-step sign_in_order, that both transactions must be signed with the caller's own key in order, that the server never sees the key, that frozen transactions expire in ~2 minutes, and a full cost breakdown (1 HBAR fee + network fees, nothing escrowed). This is exactly the extra behavioral disclosure that structured fields cannot supply.

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 critical workflow (signing package, order, expiry) is front-loaded and every clause carries operational weight. It is dense and slightly repetitive in the cost-reassurance sentences ('Cost honesty', 'Nothing is free; nothing is escrowed'), but the length is largely justified by the multi-step signing protocol.

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 complex, multi-transaction, no-output-schema tool, the description supplies everything an agent needs: the exact return shape (sign_in_order), signing requirements, expiry window, cost model, and the mandatory next call. Nothing material is left for the agent to infer.

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 100%, so the schema already documents each field; the baseline would be 3. The description adds real semantic value beyond the schema by explaining that the ticker is derived from name, that supply equals piece count, and that the caller becomes treasury, supply key, and admin, all of which affect how parameters should be chosen.

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 a specific verb+resource (create an NFT drop) and immediately scopes it: 'ONE signing package', 'any registered blockpage, agent or human', '1-10 pieces'. It clearly differentiates itself from siblings like prepare_nft_collection and finalize_nft_drop by naming its output (frozen unsigned TokenCreate bytes) and its follow-up.

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?

Strong routing: it names the follow-up ('Next: finalize_nft_drop with the two transaction ids') and explains why the mint cannot come first. It also gives conditional guidance for image_cid vs image_base64. It stops short of explicitly stating when this tool should NOT be used versus the other prepare_* siblings.

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