update_mobility_device_name

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

No annotations are present, so the description carries full responsibility for behavioral disclosure. It excels by explaining the guarded write nature, the WARNING about mutating live config, no-op detection (status='no_op'), the confirm guard that returns a current-vs-proposed preview, the environment kill-switch (UNIFI_ENABLE_MOBILITY_WRITE, off by default), and read-after verification. These details go far beyond a typical 'update' description and directly inform the caller about safety and conditional behavior.

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 information-dense and every sentence adds value, from the purpose to the safety mechanics to the parameter origins. It is somewhat long, but each clause earns its place given the guarded-write complexity. The structure could be slightly improved by separating the parameter explanations into a more formal list, but it is already well-organized and front-loaded with the most critical warning.

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 5 parameters, no annotations, and an output schema present, the description covers all necessary ground: it explains the source of IDs, the required confirmation flag, optional routing, the guarded-write behavior including the kill-switch, and the no-op/preview outcomes. Since an output schema exists, not detailing the full response structure is acceptable. The description is fully adequate for an agent to correctly invoke and interpret this tool.

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%, so the description must compensate for the schema's lack of parameter explanations. It does so comprehensively: workspace_id is tied to list_mobility_workspaces, device_id to list_mobility_devices, name is specified as 1-32 characters, confirm is explained as mandatory for applying, and key_label is described as an optional API-key routing label. Every parameter is given meaningful context beyond its type and default.

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 opens with a specific verb and resource: 'Rename a UMR device (guarded write)'. This clearly distinguishes it from sibling tools like update_mobility_device_network and update_mobility_device_wireless, which target other aspects of a mobility device. The warning 'mutates live device config' further clarifies the operation's intent.

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 provides clear prerequisites by specifying that workspace_id comes from list_mobility_workspaces and device_id from list_mobility_devices. It also explains that confirm must be true to apply the change, and mentions an optional key_label for routing. However, it does not explicitly state when to prefer this tool over alternatives like update_mobility_device_network or update_mobility_device_wireless, leaving that to inference from the tool name and stated purpose.

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