3land List For Sale

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

The description states 'operation class write' but annotations declare readOnlyHint=true, indicating it is read-only. This is a direct contradiction. Additionally, the idempotentHint=true annotation is questionable for a listing action. The description fails to add value and instead misleads.

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 relatively concise and front-loaded with the core action. However, the inclusion of 'SAP MCP context' and other meta-instructions slightly reduces conciseness. Still, most sentences serve a purpose.

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?

The description covers the main purpose and usage guidelines, but the contradiction and incorrect parameter description (priceMint) detract from completeness. The presence of an output schema reduces the need to describe return values, but the behavioral contradiction is a significant gap.

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 baseline is 3. The description mentions 'in any SPL token' which adds context to the price and priceMint parameters, but the priceMint description in the schema is incorrect ('NFT mint address' instead of token mint). No additional semantics beyond 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 clearly states the tool's function: 'List an NFT for sale on 3.Land in any SPL token.' It also contextualizes its use among sibling tools (e.g., 3land_cancelListing, 3land_buyNFT) by mentioning flows like minting, listing, cancellation, and purchase.

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?

Provides explicit guidance: 'Confirm marketplace price, seller/buyer wallet, collection, and listing state before writes' and 'Pair marketplace actions with SAP registry metadata only when the marketplace asset is part of the agent identity or service catalog.' This tells when to use and when not to use.

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