uipath_get_licenses_named_user

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

No annotations are provided, so the description carries the full burden. It discloses the data returned (user assignments, login dates, machine associations) and implies a read-only operation via 'Gets', but it does not mention authentication requirements, potential limitations, or any side effects. This is adequate but not comprehensive.

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 concise sentences that immediately state the purpose and the key output content. There is no redundant wording, and each sentence provides useful information.

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 tool with one parameter and no output schema, the description gives enough context to understand what it does and what information to expect. It does not mention response structure or any prerequisites, but these are not essential given the low complexity and the clarity of the purpose.

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?

The schema already defines the only parameter (robotType) with an enum and a description 'Type of robot to filter named-user licenses by'. The tool description merely restates that it targets a specific robot type, adding no additional context beyond the schema. Since schema coverage is 100%, the baseline is 3.

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 clearly states it retrieves named-user license details, with a specific verb ('Gets'), a specific resource ('named-user license details'), and a filtering criterion ('for a specific robot type'). It also lists what information is shown (user assignments, login dates, machine associations), which distinguishes it from sibling tools like uipath_get_licenses_runtime.

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 context for when to use the tool: when you need named-user license details filtered by robot type. However, it does not explicitly exclude alternatives or mention when not to use it (e.g., for runtime licenses). The distinction is implicit from the tool name and description.

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