merit_create_items

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

No annotations are provided, so the description must carry the burden. It discloses that the operation creates items and returns an array of {ItemId, Code}. However, it does not mention potential side effects like idempotency, validation errors, authentication requirements, or whether existing items can be overwritten. The return format is useful but the behavioral disclosure is only partial.

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 compact: two sentences that cover the operation, endpoint, required fields, conditional requirement, and return value. Information is front-loaded and there is no redundant fluff.

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 tool with a nested object array and no schema detail, the description provides the essential fields and return format, making it actionable. It lacks enumeration of optional fields and error handling, but is sufficient for basic item creation. The output schema is absent, but the return shape is described, reducing ambiguity.

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?

The input schema has a single array parameter with a generic description ('Items to create (required)'). The tool description enriches this dramatically by specifying required fields (type, usage, code, description), enum values for type and usage, and the conditional requirement (uomName for stock items). This is essential for constructing valid input and goes well beyond the schema.

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 the tool creates Merit Aktiva items, including the exact POST endpoint. The verb 'Create' and resource 'items' are specific, and it naturally distinguishes from siblings like merit_update_item and merit_create_item_groups by the action and target.

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 implies it should be used to create items but does not explicitly state when to use it versus other item-related tools (e.g., merit_update_item for changes). It provides field requirements but no context on when to select this tool over alternatives, such as prerequisites or exclusion conditions.

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