Create Delivery

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

The description states 'adds a new row' and mentions return format. Annotations already indicate non-read-only, non-destructive. The dry-run advice adds some transparency, but no details on idempotency or side effects beyond the basic creation.

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 short (3-4 sentences) and front-loaded with the core action. The only minor redundancy is the repetition of the creation concept, but overall it is efficient and well-structured.

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?

For a tool with 9 parameters and no output schema, the description lacks important context: it doesn't explain what a delivery is, the relationship with purchases, or how to perform a dry-run. The return format is covered, but prerequisites and broader context are missing.

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 78%, high, so baseline 3 applies. The description does not add extra meaning beyond the schema; it does not elaborate on parameter usage or constraints.

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 explicitly states 'Create a new delivery in NetBox' and 'adds a new row', making the purpose clear. It does not explicitly differentiate from siblings like update or delete, but the verb 'create' and the context are sufficient.

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?

Provides a key guideline: 'Ask before calling if the user wanted a dry-run.' This is helpful for a mutation tool. However, it does not mention when to use this tool versus alternatives (e.g., list_deliveries or get_delivery) or specify prerequisites (e.g., purchase must exist).

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