Create Article

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

The description is consistent with annotations (readOnlyHint=false, destructiveHint=false) but adds no additional behavioral context. It does not disclose side effects, return behavior, or consequences of creation (e.g., duplicates, ID generation). The annotations already cover safety but the description should add value.

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 short sentence but is under-specified. It is concise but not informative, failing to front-load key details that would help an agent use the tool correctly.

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 extremely incomplete given the tool's complexity (nested object with important fields like type, unitPrice). It does not explain what an article is in the Lexware context, nor does it mention return values or behavior. The schema provides some info but the description fails to add context.

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% as the input schema already describes the 'body' parameter and its key fields. The description adds no extra meaning beyond what the schema provides. With full coverage, baseline is 3.

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 'Create a new article.' is a tautology of the tool name 'lexware_create_article'. It fails to specify what an article is (e.g., product or service in Lexware) and does not distinguish this from other create tools like lexware_create_contact or lexware_create_invoice.

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 usage guidance provided. The description does not indicate when to use this tool over alternatives, such as when to create an article versus a contact or invoice. No prerequisites or context are mentioned.

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