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

Annotations already communicate read-only, idempotent, and non-destructive behavior. The description goes beyond them by disclosing a hard constraint, the $0.01 USD per-call cost, and the Magic Eden dependency, which an agent needs to know before invoking.

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 entire guidance is one front-loaded sentence with the cost and the action. No wasted words and no repetition of schema details.

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 one-parameter tool with annotations and a documented payment parameter, the description is adequate, but it does not describe what the search returns or any result limitations. The agent can select the tool confidently, though the absence of output information leaves a mild gap in invocation expectations.

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 description coverage is 100%, so the payment-proof parameter is already fully documented in the input schema. The tool description adds no parameter-level detail, and at 100% coverage it does not need to.

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 states a clear verb and resource: it searches NFT collections, and narrows scope with 'across Solana via Magic Eden.' It is unambiguous but does not explicitly distinguish itself from sibling tools such as market_intelligence or providers, so it stops short of a 5.

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?

There is no explicit when-to-use or when-not-to-use statement, but the scope 'across Solana via Magic Eden' implies the intended context for selecting this tool. It does not name alternatives or exclusion conditions.

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