beel_create_product

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

Annotations already mark readOnlyHint=false (mutation) and destructiveHint=false. The description reinforces mutation by saying 'creates', but adds no extra behavioral context like side effects, idempotency behavior, or response format beyond what the schema's idempotency_key description already provides. No contradiction with annotations.

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 concise sentences, front-loaded with the purpose and then a redundant endpoint line. No fluff, could drop the endpoint for slight improvement.

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 create operation with no output schema, the description doesn't mention success behavior or prerequisites. However, the complex tax rules are fully documented in the schema's nested $defs, so the description itself is minimally sufficient, though it leaves the agent to dig deep into the schema.

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 67%, and the description does not add any parameter-level meaning beyond what the schema already provides. The mention of 'company (NIF)' echoes the existing company_id description. With moderate coverage, the description could have compensated but doesn't.

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 clear verb ('creates') and resource ('product or service'), and scopes it to 'this company (NIF)'. It distinguishes from bulk creation only by name, not explicitly, so it's clear but not fully differentiated from 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?

The description gives no guidance on when to use this versus `beel_create_products_bulk` or when not to use it. No prerequisites (e.g., company existence) are mentioned. Usage context is implied at best.

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