create_product

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

The description adds no behavioral context beyond what annotations already provide. Annotations indicate readOnlyHint=false (mutation), destructiveHint=false, idempotentHint=false, and openWorldHint=true. The description does not disclose side effects, authorization requirements, or response behavior, which is a gap for a creation 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?

The description is a single sentence that directly states the tool's purpose without extraneous words. It is front-loaded and efficiently conveys the core function. While short, it is not overly terse given the schema covers details.

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?

The description is insufficient for the tool's complexity: 10 parameters, no output schema, and no error handling or return value information. It does not explain typical usage scenarios, default values, or constraints, making it incomplete for an AI agent to use confidently.

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?

Since schema description coverage is 100%, the baseline is 3. The tool description does not elaborate on parameters beyond the schema; it only states the overall purpose. The parameter descriptions in the schema are comprehensive, so the description adds no additional semantic value.

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 'Új termék/szolgáltatás létrehozása' clearly states the action (create) and resource (product/service). It is specific enough to distinguish from other creation tools like 'create_partner' or 'create_spending', though it does not explicitly differentiate by resource type. The purpose is clear 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?

No guidance is provided on when to use this tool over alternatives, such as when to create a product versus a partner or spending. The description does not mention context, prerequisites, or exclusions, leaving the agent without decision-making support.

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