create_product

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

With no annotations, the description explains key behaviors: the product UUID is reused by other charges, value is in decimal BRL, pixAutomatic only affects subscription checkouts, and idempotency key ensures safe retries. It does not mention permissions or error handling.

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 a single dense paragraph but is front-loaded with purpose and efficiently conveys key points. It could benefit from slight restructuring (e.g., bullet points for clarity), but every sentence adds value.

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 16 parameters (all documented in schema) and no output schema, the description covers critical behavioral details like value units and idempotency. It does not describe return structure or error conditions, but these are secondary to the main purpose.

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 coverage is 100%, so the description adds value by explaining the value unit (decimal BRL), the subscription-specific use of pixAutomatic, and the retry safety of idempotencyKey, which are not obvious from schema descriptions alone.

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 'Create a product for the authenticated seller', specifying the action and target. It distinguishes from siblings like create_pix_charge and create_boleto_charge by focusing on product creation.

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 provides clear context for when to use the tool, including value format, idempotency, and pixAutomatic behavior. However, it does not explicitly state when NOT to use it or list alternative tools for similar tasks.

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