Create Voucher

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

Annotations provide only basic hints (readOnlyHint=false, destructiveHint=false, idempotentHint=false), and the description adds no behavioral context. Important details like duplicate handling, validation, or side effects are missing, leaving the agent with insufficient understanding of the tool's behavior.

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, which is concise but lacks critical information that would make it earn its place. It is not wasteful, but it is insufficiently informative for an agent to use the tool correctly among many siblings.

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?

Given the complexity of multiple sibling tools and a nested parameter with no output schema, the description is too brief. It fails to explain the tool's role relative to other create tools or what the return value looks like, leaving a significant knowledge gap.

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 already covers 100% of parameters with a description listing key fields, so the tool description adds no additional meaning beyond the schema. The parameter semantics are adequate but not enhanced.

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 a 'new bookkeeping voucher' in Lexware, identifying the specific verb and resource. However, it does not distinguish this tool from sibling tools like lexware_create_invoice or lexware_create_credit_note, which could create confusion about when to use each.

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 provides no guidance on when to use this tool versus alternatives. Given the many sibling create tools for specific voucher types (e.g., invoice, credit note), this omission forces the agent to infer usage from the schema's 'type' field, which is not explicitly mentioned.

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