Create Location

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

Annotations already indicate readOnlyHint=false and destructiveHint=false. The description adds 'This adds a new row to NetBox' confirming a write operation, and the dry-run advice adds behavioral context. However, no further details on side effects, authentication, or rate limits are given.

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 very concise: two sentences plus a returns section. The purpose is front-loaded, the cautionary note is placed second, and the return format is clearly explained without extra fluff.

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 create tool with 12 parameters and no output schema, the description covers the core purpose, a usage caution, and return format options. It does not detail required parameters or relationships (e.g., site id), but given the schema descriptions cover those, this is acceptable.

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 75%, so baseline is 3. The description adds value by explaining the response_format parameter's usage: 'Use ''json'' when chaining follow-up tool calls.' This goes beyond the schema's enum listing and provides practical guidance.

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 verb ('Create') and resource ('a new location in NetBox'), and the title 'Create Location' is consistent. It distinguishes from sibling tools like netbox_list_locations, netbox_get_location, etc. by implying creation as the core action.

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 explicitly provides a usage guideline: 'Ask before calling if the user wanted a dry-run.' This shows appropriate caution. It does not explicitly contrast with alternatives but the purpose is clear enough to select this tool when creating a location.

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