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

No annotations provided, so description carries full burden. Mentions 'pins the burn ixs + fee per tx' and returns outcomes, but does not disclose failure behavior, idempotency, or destructive nature (burning is inherently destructive but not stated).

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?

Two concise sentences, no unnecessary words. Front-loaded with the main action. Could be slightly more structured but very efficient.

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, but description only vaguely mentions 'Returns per-tx outcomes' without describing the format or error handling. For a submission tool in a large sibling group, more context is needed (e.g., what happens on failure, confirmation behavior).

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 parameters are well-documented in the schema itself. Description does not add significant new meaning beyond what's already in the schema's descriptions.

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?

Clearly states 'Submit burn-nft tx(s) (signed)' with specific verb 'Submit' and resource 'burn-nft transactions'. Distinguishes from sibling tools like build and list by mentioning signed transactions and referencing the /build call.

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?

Implies use after building by referencing signed transactions and the /build call, but no explicit guidance on when to use or not use this tool vs alternatives like solknife_burn_nft_build.

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