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

With no annotations, the description must fully disclose behavior. 'Chunked' hints at splitting into multiple transactions but does not explain what 'chunked' means (e.g., batch size limit). There is no mention of side effects, signature requirements, or output format.

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 a single sentence with no wasted words. It conveys the core purpose efficiently, though 'chunked' could be expanded without losing conciseness.

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?

No output schema is provided, and the description does not indicate what the tool returns (e.g., transaction data). Given the tool builds transaction(s) for a complex blockchain operation, the description lacks critical context about the output and subsequent steps.

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 50% (only descriptions for addresses). The description does not explain how 'mints' relates to 'selected NFTs' nor the role of 'owner'. No additional context is provided beyond 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 uses a specific verb 'Build' and resource 'burn tx(s) for selected NFTs', which clearly indicates the tool prepares burn transactions. It also mentions pNFTs support. However, it does not explicitly distinguish from sibling tools like solknife_burn_nft_execute or solknife_burn_nft_list.

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?

No guidance on when to use this tool vs alternatives. It does not explain that the built transactions are intended for subsequent execution by solknife_burn_nft_execute, leaving the usage flow ambiguous.

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