unifi_rename_device

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

Annotations already declare destructiveHint=true, and the description reinforces and extends this by disclosing the dual preview/execute mode (dry_run defaults to True), the requirement for explicit user consent before executing, and API key authentication. This adds meaningful behavioral context beyond the structured annotations without contradicting them.

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?

Two short sentences with zero wasted words. The core behavior (preview/rename) is front-loaded, followed by the execution gate and prerequisite. Every clause earns its place.

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?

The output schema covers return values, and the description carries the essential operational facts: default preview mode, explicit consent required to execute, and API key requirement. Potential side effects of an actual rename are not mentioned, but for correct tool invocation the described information is largely sufficient.

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?

With 0% schema description coverage, the description must compensate, and it does explain the critical dry_run parameter's role in preview vs. execution. However, it does not add meaning for device_id, name, or site; these are left to their self-evident names and schema constraints, which is adequate but not a full compensation for zero coverage.

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 the operation ('Preview a rename... Execute only with user intent and dry_run=False') with a specific verb and resource tied to the tool name. It clearly distinguishes this as the only mutation tool among read-only list/get/locate siblings, though 'Preview a rename' is slightly indirect phrasing for what is fundamentally a rename operation.

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 conditions for execution: user intent must be present and dry_run must be False, plus the API key prerequisite. It doesn't name alternatives or exclusion conditions, but no genuine alternative exists among siblings (all are read-only), so the preview-versus-execute guidance is the key usage decision and it is stated clearly.

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