Add a product

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

Annotations only declare readOnlyHint=false, so the description must carry the rest. It implies persistence but says nothing about scope (which brand/account the product attaches to), duplicate handling, required prior context, or what happens on success. The phrase "from its product page" adds a small amount of source context but no behavioral depth.

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?

A single front-loaded sentence with no filler; the verb and object come first and nothing is repeated from the title. There is no wasted text.

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 zero-parameter tool with no output schema, the description covers the basic idea but leaves the core operational question unanswered: how the specific product is identified or scoped if nothing is passed. It is minimally adequate rather than complete.

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 zero declared parameters the baseline is 4, but the description names fields ("name, price and photos") that do not appear anywhere in the schema, which declares no properties and allows additionalProperties. That hint is useful but sits in tension with the schema rather than clarifying it.

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 gives a concrete verb and resource ("Save ... your products") and distinguishes the product object from the sibling add_brand/save_my_brand tools. It is clear what the tool acts on, though it never explains the mechanism by which a product is selected, since the schema declares no parameters.

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?

There is no statement of when to use this tool versus list_my_products, remove_product, or add_brand, and no prerequisites or exclusions. "From its product page" hints at context but does not tell an agent under what conditions to call it.

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