Create Power_outlet_template

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

Annotations indicate it's a write operation (readOnlyHint=false) and not destructive. The description adds context by stating 'This adds a new row to NetBox' and advising a dry-run check, which goes beyond the annotations. It also describes return format options.

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 three sentences: purpose, caution, and return format. It is succinct, front-loaded, and every sentence provides essential information without waste.

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 the parameter count (8) and no output schema, the description covers creation behavior, return options, and a caution. It lacks an explanation of the concept of a power outlet template (e.g., its relation to device types), but the required parameters are clear from the schema. Overall, fairly complete.

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 75%, and the description does not elaborate on parameters beyond what the schema already provides. The schema itself has decent descriptions, so the description adds little extra meaning. With high coverage, baseline 3 is appropriate.

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 power_outlet_template in NetBox.' It uses a specific verb (create) and resource (power_outlet_template), distinguishing it clearly from other create tools in the sibling list.

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 advises to 'Ask before calling if the user wanted a dry-run,' which provides a cautionary guideline. However, it does not specify when to use this tool versus alternatives like creating power outlets or other templates, nor does it outline any prerequisites.

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