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

With no annotations, the description carries the full load and does disclose non-obvious behavior: it returns unsigned transactions rather than executing, the tokens never leave the seller's wallet, and the market is authorization-based with no custody. It omits what the returned payload looks like, chain/network assumptions, and whether the approve step is skipped when already approved.

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 compact sentences with the action and step sequence front-loaded, followed by the custody clarification. Every clause adds information; nothing is padding.

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 prepare-only tool with no output schema or annotations, the description covers the action, the two underlying transactions, and the key custody semantics. Remaining gaps (return shape of the unsigned tx array, chain, approval-already-exists case) are minor but real.

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% and both parameters are documented with examples, so the schema does the heavy lifting. The description adds only the 'list(amount, priceWei)' mapping and per-token price framing, which is marginal value beyond the schema's 'BNB price per 1 SHANIU'.

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?

Uses a specific verb+resource: 'Prepare unsigned transactions to list SHANIU for sale', and even enumerates the internal steps (approve, then list(amount, priceWei)). It does not explicitly name a sibling such as shaniu_prepare_buy, but the 'for sale' scoping naturally separates it from buy/claim variants.

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 two-step flow (approve the market contract, then list) implies when the tool is invoked, but there is no explicit statement of prerequisites (e.g., must the seller hold SHANIU, is approval needed if already granted) or when to prefer this over shaniu_prepare_buy/prepare_claim. Usage is inferable rather than stated.

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