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

Annotations already declare readOnlyHint=false, idempotentHint=false and openWorldHint=true, so the mutating and non-idempotent nature is structured data, not new information. The description reinforces the write semantics and adds the endpoint (POST /items), which is minor extra context; it says nothing about retry safety, what happens on duplicate names, or auth requirements.

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?

A single compact sentence with the operation and scope front-loaded and zero filler. The trailing 'POST /items' is arguably irrelevant to an agent invoking an MCP tool but is harmless and short.

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 six-parameter create tool with full schema coverage, optimistic-write annotations, and no output schema, the essentials are covered: what is created, in what domain, and its fields. Missing niceties (currency default, unit lookup, required-field emphasis) are all already available in 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 100%, so the schema already documents all six fields including the currency default (BGN) and the quantity_unit cross-reference to invbg_list_item_units. The description merely echoes name/price/unit and adds no format or constraint detail beyond the schema, so baseline 3 applies.

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 the specific verb+resource ('add a product or service to the catalogue') and prefixes it with 'WRITE', which cleanly separates it from read siblings like invbg_list_items and invbg_get_item. It does not name those siblings explicitly, but the create-vs-read distinction is unmistakable.

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 when-to-use or when-not-to-use guidance and names no alternatives. An agent can infer it is the create counterpart to invbg_update_client-style tools, but nothing is stated about prerequisites, duplicate handling, or how it relates to invbg_create_invoice.

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