add_store_item

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

No annotations are provided, so the description carries the full behavioral burden. It hints at the scout-then-add workflow and the merchant-review implication of source_url, but says nothing about duplicate handling, required permissions, what happens on failure, or what the call returns for this 10-parameter mutation.

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 sentences, no filler. The core action and payload come first, and the source_url directive follows as an actionable constraint rather than preamble.

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 10-parameter, 5-required mutation tool with no annotations and no output schema, the description covers only a subset of the parameters and none of the failure or return behavior. The schema is rich, which limits the damage, but the definition is not fully self-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?

Schema description coverage is 100%, so the schema already documents all ten parameters and a baseline of 3 applies. The description adds mild emphasis by calling out price, curator_note, delivery guarantee and source_url, but it adds no format, range, or default information beyond the schema.

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 and resource ('Add a new scouted item ... to your store') and names the salient payload fields. It is distinguishable from update_store_item/delete_store_item by the 'new' qualifier, though it never explicitly contrasts itself with those siblings.

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?

'Always specify source_url so the merchant can review supplier information' gives a concrete precondition for calling it. However, there is no guidance on when to use this versus update_store_item, nor any exclusion or prerequisite (e.g. whether the store must exist first).

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