setSwitchPortProfile

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

The annotations mark destructiveHint=true and the description's 'Assign' is consistent with a mutating operation, so there is no contradiction. However, the description adds no behavioral detail beyond that: it does not disclose whether the existing profile is overwritten, whether the LAN profile must already exist, or what side effects may occur.

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 a single, efficient sentence with no unnecessary words. The key scoping word 'single' appears early, and the sentence is easy to parse, though it sacrifices useful detail for brevity.

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?

With four parameters, zero schema descriptions, no output schema, and only a destructive hint, the description is too minimal to support reliable tool usage. It fails to define parameter semantics or selection criteria, leaving important gaps in 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 0%, and the description does not explain switchMac, port, profileId, or siteId beyond the generic terms 'LAN profile' and 'switch port.' An agent cannot infer the role of each parameter or how to fill them correctly from the 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 states a specific verb and resource: 'Assign a LAN profile to a single switch port.' The 'single' qualifier distinguishes it from batch operations like batchSetSwitchPortProfile, though it does not explicitly contrast with setSwitchPortProfileOverride.

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?

There is no guidance on when to use this tool over alternatives such as setSwitchPortProfileOverride, batchSetSwitchPortProfile, or updateSwitchPort. No context, prerequisites, or exclusions are provided, leaving the agent to guess from sibling names.

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