draft_item

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

The description describes write operations (creating a draft and taking a screenshot) while the annotation readOnlyHint is true, creating a direct contradiction. This significantly undermines transparency.

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, but the mixed language (Chinese and English) and lack of strict formatting slightly reduce clarity. Nonetheless, it conveys essential information without unnecessary fluff.

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?

Given an output schema exists, the description covers the return value (screenshot path) well. It explains the auto-screenshot behavior, which is key. Minor gaps include lack of error handling details, but overall sufficient.

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?

With 0% schema description coverage, the description provides valuable semantics for all three parameters: image (local path or URL), description (text), and price (default 100). This goes beyond the schema's bare fields.

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 it fills a draft on Xianyu with fields including image, description, and price, and then takes a screenshot. It also references the sibling publish_item for formal release, distinguishing its role.

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 description explicitly instructs to confirm the draft and then call publish_item for formal release, providing clear usage context. However, it does not mention scenarios where drafting is inappropriate or alternatives like manage_item.

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