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

Discloses write-time behavior beyond the annotations: payload validation against the leaf category spec and return policy, plus the restricted-goods classifier that leaves flagged listings inserted but invisible until cleared. This is valuable because the annotations only indicate non-readOnly and provide no moderation or visibility context.

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?

Three sentences, front-loaded with the core action followed by two high-value caveats. No redundancy with the schema and no filler.

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 complex 17-parameter create tool with no output schema, the description covers the non-obvious side effects: validation and moderation queueing. It could mention the return value or resulting listing identifier, but the essential call contract is clear from schema and description together.

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 every parameter is already documented. The description's validation note mostly restates schema details for specs and return_policy, adding little new parameter-level meaning.

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?

States a specific verb ('Create') and resource ('product listing'), which clearly differentiates it from siblings like seller_update_listing, seller_archive_listing, and services_create_listing. The validation and moderation details reinforce that this is the listing-creation entry point.

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 create verb implies initial listing creation versus updating or archiving, but the description gives no explicit when-to-use/when-not-to-use guidance. It does not name alternatives such as services_create_listing for service listings or seller_update_listing for changes.

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