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

The description claims 'Read-shaped tools only (anything that buys, sells or writes refuses)', which directly contradicts the annotation readOnlyHint=false. This is a serious inconsistency: an agent relying on annotations would expect possible state changes, while the description promises read-only behavior. The added details about 'finalized commitment' and 'data comes back as it is' are useful, but the contradiction forces a score of 1.

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 core purpose is front-loaded and the description is reasonably compact. However, the truncated sentence and the inclusion of promotional/contextual material ('a live seat on The Wall', listing URL) add noise without earning their place. The structure is adequate but not tight.

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?

There is no output schema, and the description does not explain the return value or how the burn verification result is presented. The parameter guidance is incomplete due to truncation, and the contradiction between read-only claims and annotations leaves the agent uncertain about side effects. For a verification tool, this is not enough context to call it confidently.

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 input schema defines no parameters, so the description is the only source of parameter meaning. It does mention passing `mint` and optionally `owner`, which is helpful, but the sentence is truncated before naming the third parameter. With zero schema parameters, the description partially compensates but remains incomplete.

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's purpose: confirming that a Solana transaction burned a token, and identifies the key facts it reports (mint, owner, amount, finalized commitment). This distinguishes it from generic transaction or history tools. However, the description is truncated mid-sentence ('and a `'), which slightly undermines completeness.

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 implies when to use the tool: when you need to verify a burn event on Solana at finalized commitment. It also adds a general constraint that the server only exposes read-shaped tools. However, it does not explicitly name alternative tools or state when not to use this one, leaving the routing decision somewhat implicit.

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