Update Power_port_template

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

Annotations indicate destructiveHint=true and idempotentHint=true, which align with the update semantics. The description adds that it uses PATCH semantics (partial update) and returns Markdown or JSON, providing context beyond the annotations.

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?

Three concise sentences: purpose+semantics, usage instructions, and return format. No wasted words, front-loaded with key information.

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 9 parameters and low schema coverage, the description covers the core usage (id and PATCH) and return options. However, it does not explain what a power_port_template is or the meaning of many fields, which may be needed for correct usage.

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 only 22%; only 'id' and 'response_format' have descriptions. The description adds that 'id' is numeric and that only provided fields change, but most other parameters lack semantic meaning in both schema and description.

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 'Update', the resource 'power_port_template', and the semantics 'PATCH semantics — only provided fields are changed'. This sufficiently distinguishes it from sibling update tools for other NetBox objects.

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 instructs to supply the numeric 'id' and only the fields to change, omitting fields leaves them unchanged. It does not explicitly mention when not to use this tool or provide alternatives, but the guidance is clear and actionable.

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