Create Rack_reservation

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

Annotations indicate a write operation (readOnlyHint=false) but no destructive effect (destructiveHint=false). The description adds that it adds a new row to NetBox and explains the return format (markdown or JSON). This provides some context beyond annotations, but lacks details on side effects, error conditions, or required permissions.

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: three sentences with no fluff. The purpose is in the first sentence, followed by a call to action and return format. All information is relevant 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?

With 9 parameters and a domain-specific concept (rack reservation), the description is minimal. It does not explain what a rack reservation is, the meaning of 'units', how custom_fields work, or any constraints. The return format is covered, but overall the tool lacks sufficient context for an agent to use it confidently without prior knowledge.

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 high (78%, 7 of 9 params documented). The description adds no parameter-level details beyond what the schema already provides. Baseline 3 is appropriate as the schema carries most of the burden.

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 'Create a new rack_reservation in NetBox.' It uses a specific verb and resource, and distinguishes from sibling tools like netbox_get_rack_reservation, netbox_update_rack_reservation, and netbox_delete_rack_reservation. The action is unambiguous.

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 only usage guideline is 'Ask before calling if the user wanted a dry-run.' There is no guidance on when to use this tool versus alternatives, such as netbox_update_rack_reservation for modifying an existing reservation, or which prerequisites (e.g., existing rack, user) are needed. The instruction is helpful but insufficient.

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