3land Cancel Listing

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

Annotations already declare destructiveHint=true and readOnlyHint=false. The description adds 'operation class write' which is redundant. Does not disclose additional behaviors like authentication, side effects, or rate limits.

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?

Reasonably concise with front-loaded purpose. The SAP MCP context adds some verbosity but overall structure is clear and minimal.

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?

Adquate given output schema and annotations. Lacks details on prerequisites (e.g., ownership of listing) and return behavior, but the cautionary note partially compensates.

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% with clear descriptions for both seller and listingId. The description does not add further meaning beyond the schema, so baseline score applies.

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 the action: 'Cancel an active NFT listing on 3.Land.' The verb 'cancel' and resource 'active NFT listing' are specific. Distinguishes from sibling tools like 3land_listForSale and 3land_buyNFT.

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?

Broadly mentions using for '3.Land NFT collection, minting, listing, cancellation, and purchase flows' but does not explicitly define when to use or alternatives. Precautionary notes are included but no exclusions.

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