Update Console_server_port_template

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

Annotations already indicate destructiveHint=true and readOnlyHint=false, so the description does not need to reiterate mutation. It adds value by explaining PATCH semantics and return format behavior. No contradiction with 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?

The description is three sentences, each serving a distinct purpose: purpose/semantics, usage guidance, and return format. It is front-loaded with the most critical information and contains no redundant words.

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 complexity (8 parameters, no output schema), the description covers purpose, semantics, usage, and return format. It lacks domain context (e.g., what a console_server_port_template is, relationships to other objects) but is sufficient for an agent that understands NetBox context.

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 low (25%). The description adds meaning for the 'id' and 'response_format' parameters, but does not provide additional context for other parameters (e.g., name, type, device_type) beyond basic schema constraints. It partially compensates but could be richer.

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 action ('update an existing console_server_port_template') and the semantics ('PATCH semantics — only provided fields are changed'). This distinguishes it from sibling tools like create, get, list, and delete for the same resource.

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 gives explicit guidance: 'Supply the numeric id and only the fields you want to change. Omitting a field leaves it unchanged.' It also mentions return format options. However, it does not explicitly state when not to use this tool or provide direct comparisons to siblings.

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