Rename port

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

Annotations already convey readOnlyHint=false, destructiveHint=false, and idempotentHint=true. The description adds a useful behavioral guarantee that mode and power are unaffected, but it does not disclose the user_authorized approval requirement or any other operational caveats. This is similar to the calibrated baseline where the description adds some value but not rich behavioral context.

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 two short sentences with zero filler. The primary purpose is front-loaded, and the key exclusion is stated immediately after.

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 simple rename operation, the combination of the description, rich input schema, and annotations covers almost everything needed. The only notable gap is that the mandatory user_authorized=true requirement is buried in the schema rather than surfaced in the tool description, which an agent could miss during initial selection.

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 100%, so the input schema already documents all parameters. The tool description adds no additional parameter-level meaning beyond what the schema provides, so the baseline score of 3 applies.

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 states a specific verb and resource: 'Rename a port' with the clarifying parenthetical 'the label shown in the AC Infinity app'. It also explicitly distinguishes the tool from sibling set_port_mode/set_port_power tools by saying 'Does not change any mode or power'.

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 a clear when-to-use context: renaming a port label. It also includes an explicit when-not exclusion ('Does not change any mode or power'), but it does not name alternative sibling tools or state that user_authorized must be true before invoking.

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