Create Dunning

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

Annotations already indicate write operation and possible side effects (openWorldHint=true), but the description adds no additional behavioral context about what happens upon creation (e.g., system updates, triggers).

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?

Extremely concise: one sentence plus a brief list of key fields, no fluff. Easy to parse and front-loaded.

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 creating a dunning (nested object, no output schema), the description provides an overview but lacks details on required subfields, validation, and return values. It relies on external API docs, which is acceptable but not complete.

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 description lists key fields within the body parameter (voucherDate, address, lineItems, etc.), adding meaningful structure beyond the vague schema definition (propertyNames, additionalProperties). This helps the agent construct the JSON body.

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 action (create) and the target resource (dunning) within Lexware. It distinguishes from sibling tools by resource name, but lacks additional differentiation details.

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 on when to use this tool versus alternatives like creating an invoice or credit note. No prerequisites or context provided.

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