Create Inventory_item_group

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

Annotations already mark readOnlyHint=false, so the description's mention that 'This adds a new row to NetBox' is consistent but adds limited value. The description does not disclose additional behavioral traits such as required permissions, error behaviors, or side effects beyond what annotations imply.

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, with two sentences for purpose and a guideline, plus a return format note. It is front-loaded but includes minor redundancy ('Create a new inventory_item_group' and 'This adds a new row'). Overall efficient.

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 7 parameters including nested objects (custom_fields) and no output schema, the description covers the basic purpose and a usage hint but lacks details on how to use parameters, examples, or behavior around parent relationships. Adequate but not comprehensive.

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 (71%), so the baseline is 3. The description does not elaborate on parameter meanings beyond the schema, though it briefly mentions return formats which relate to response_format. No additional parameter context is provided.

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 inventory_item_group in NetBox', which is a specific verb-resource pair. It differentiates from sibling tools that list, get, update, or delete inventory item groups, and the purpose 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 description includes a guideline to ask before calling if the user wanted a dry-run, but provides no guidance on when to use this tool versus alternatives like netbox_update_inventory_item_group or netbox_list_inventory_item_groups. It lacks context about prerequisites or conditions for use.

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