Add a product card

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

Consistent with readOnlyHint=false (it's a write operation). Adds the plan requirement as a constraint, but does not disclose other potential side effects (e.g., whether adding an existing product overwrites or errors). The description goes slightly beyond annotations by noting the plan prerequisite, but not significantly.

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?

Extremely concise and to the point. One sentence conveys the action, purpose, and a key prerequisite with no unnecessary words or repetition.

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?

Sufficient for a simple add operation. It explains the outcome (product card for chatbot) and the plan requirement, though it omits details about return values or error handling. Given no output schema and simple nature, it is adequately 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?

Schema covers 100% of parameters with individual descriptions, so the baseline is 3. The description does not add any extra meaning beyond what the schema already provides for parameters like name, price, image_url, etc.

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?

Clearly states the action ('Add a product') and the purpose ('the chatbot can show as a card'), distinguishing it from sibling tools like list_products or delete_product. The one-sentence description is specific and unambiguous.

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?

Provides a prerequisite ('Needs the Standard plan or higher') but does not explicitly mention when to use this tool over alternatives (e.g., no reference to update_product or import tools). The plan requirement is useful context, but the description lacks guidance on when not to use it.

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