unifi_list_radius_profiles

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

Annotations already declare readOnlyHint=true and destructiveHint=false, covering the safety profile. The description adds useful domain context about what RADIUS profiles are referenced by, but does not disclose additional behavioral traits such as pagination limits or authentication requirements. This is adequate but not rich.

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, focused sentence followed by a brief return-value note. It front-loads the core action and uses no filler words, making it easy for an agent to parse quickly.

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 list operation with a required siteId, four well-documented parameters, read-only annotations, and an output schema, the description adds enough domain context to be complete. It explains the resource's role while the structured fields handle the remaining details.

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 all four parameters are already documented with meaningful descriptions. The tool description does not add parameter-specific details, but the schema carries the full burden. A baseline of 3 is appropriate here.

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 ('List RADIUS profiles') and clarifies the domain by explaining these are auth/accounting server configurations referenced by WiFi WPA-Enterprise, switch 802.1X port auth, and VPN. This clearly distinguishes it from the many sibling list/get tools, which target different UniFi resources.

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 parenthetical explanation gives clear context for when this tool is relevant: managing RADIUS profiles used in enterprise WiFi, 802.1X switch authentication, and VPN. It does not explicitly name exclusions or alternatives, but no obvious sibling tool duplicates this resource, so the guidance is sufficient.

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