Create listing

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

The description discloses that the tool modifies live shop data and requires explicit confirmation, adding behavioral context beyond annotations (readOnlyHint=false, destructiveHint=false). This helps the agent understand the mutation's sensitivity.

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 extremely concise with two sentences, front-loading the main action and critical sensitivity warning. Every word adds value, with no redundancy.

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 the complexity (10 parameters, no output schema, low schema coverage), the description is too minimal. It does not explain return behavior, missing parameters, or how to handle the confirmation flow, leaving significant gaps.

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 only 30% schema description coverage, the description adds no parameter-specific details. Required parameters like name, price, stock, and category_id remain undocumented beyond the schema, failing to compensate for the low coverage.

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 verb 'Create' and the resource 'new product listing in the shop,' accurately reflecting the tool's function. It distinguishes from sibling tools like update_listing or delete_listing.

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 notes that the action is sensitive and requires confirmation, implying cautious use. However, it lacks explicit guidance on when to use this tool versus alternatives (e.g., update_listing) and does not outline prerequisites.

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