create_product

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

No annotations are supplied, so the description carries the full behavioral burden, yet it only says it creates a catalog entry. It does not mention duplicate-name handling, validation failures, required business fields, permissions, or reversibility — all relevant for an unannotated mutation tool.

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 short sentences with the action front-loaded and no filler. However, the extreme brevity leaves the bulk of the payload unexplained, so conciseness comes at the cost of usefulness.

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?

With a nested, completely undocumented `data` object, no output schema, and no annotations, the description should explain at least the shape or key fields of the product payload. Instead it defers entirely to external API documentation an agent may not have access to.

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 50%: company_id is documented in the schema with its default fallback, but `data` is an open object with no property documentation. The description only points to 'the Fatture in Cloud API v2 schema', which is an external reference rather than inline meaning, so it does not compensate for the undocumented nested payload.

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 ('Crea un prodotto o servizio a listino'), which clearly distinguishes it from siblings like update_product or create_client. It does not explicitly name alternatives, but the verb+resource pair is 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?

There is no guidance on when to use this versus update_product, list_products, or create_client/create_supplier, and no mention of prerequisites such as needing an existing price list or company context. The agent must infer the entire usage context from the tool name.

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