uipath_get_licenses_runtime

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

With no annotations, the description carries the full burden. It discloses read-only intent via 'Gets' and describes the output fields (machine assignments, runtimes, online status). However, it does not mention prerequisites, permissions, rate limits, or any potential side effects, leaving some behavioral gaps.

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 sentences, front-loaded with the primary action, and every phrase adds value. No filler or redundant content.

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 getter with one enum parameter and no output schema, the description adequately conveys purpose and output summary. It could be more complete by describing the response structure or any limitations, but it covers the essential information needed for basic use.

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 provides 100% coverage for the only parameter (robotType) with a description and enum. The tool description adds no additional semantic detail beyond restating 'for a specific robot type', so the baseline score of 3 is appropriate.

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 'Gets runtime license details for a specific robot type' and specifies the output ('Shows machine assignments, runtimes, and online status'). This distinguishes it from sibling license tools like uipath_get_licenses_named_user and uipath_get_license_stats by focusing on runtime licenses and robot-type filtering.

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 implies usage context (needed when you want runtime license details for a specific robot type) but does not explicitly mention when to use this tool versus alternatives. It does not name sibling tools or provide exclusions, so guidance is only implied.

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