bexio Deliveries

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

Annotations indicate readOnlyHint=false and destructiveHint=false. The description adds transparency by detailing that issue finalizes the delivery note and adjusts stock when stock management is active, and mentions status codes for draft vs done. This goes beyond annotations.

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 concise: two sentences and a structured list of actions. It is front-loaded with purpose and immediately provides actionable details. No superfluous text.

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?

Without an output schema, the description adequately covers the three actions and their parameters. It mentions that get includes positions and issue adjusts stock. However, details about response format or pagination defaults are missing, but overall sufficient for an agent to use the tool.

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 coverage is 100%, so baseline is 3. The description adds value by explaining which actions require the id parameter, listing valid order_by fields, and clarifying the effect of issue. This context enriches the schema definitions.

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 reads and issues delivery notes, and specifies three actions. It distinguishes from sibling tools by mentioning that deliveries are created from orders via bexio_orders, but does not explicitly differentiate from other related tools like bexio_stock.

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 explains when to use each action (list, get, issue) and provides context such as optional parameters and the effect of issue. It refers to bexio_orders for creation, giving guidance on alternatives, but does not explicitly state when not to use certain actions.

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