create_delivery_note

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

The description "Creates new delivery note" aligns with annotations (readOnlyHint=false, destructiveHint=false) but adds no behavioral details beyond what annotations already convey. It does not specify side effects, permission requirements, or state changes.

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 extremely concise at three words. It is front-loaded and contains no unnecessary content. However, it could be slightly expanded without losing conciseness to add context.

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 (19 parameters, 6 required, no output schema), the description is too minimal. It does not explain what happens after creation (e.g., returned data), any default behaviors, or how to interpret the result. The tool's completeness is insufficient for an agent to fully understand its usage.

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 input schema already documents all parameters adequately. The description adds no further parameter information, so it meets the baseline of 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 "Creates new delivery note" clearly identifies the action (create) and the resource (delivery note). It is not a tautology and distinguishes from other create_* tools among siblings. However, it lacks any additional context about what a delivery note entails.

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 like create_invoice or create_letter. There is no mention of prerequisites, conditions, or exclusions.

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