uipath_get_license_stats

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

With no annotations provided, the description carries the full burden. It discloses an important prerequisite (License.View permission) and adds temporal context ('over time'). It could mention response structure or pagination, but for a simple read-only stats tool, the disclosed traits are valuable and go beyond a tautological getter.

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 short sentences, front-loading the purpose and including the permission requirement without any filler. Every word contributes to the agent's understanding.

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 2 optional parameters, no output schema, and no annotations, the description provides enough context: what it gets, the permission needed, and the data shape ('robot counts by type over time'). It is slightly weaker in explaining return formatting, but that is not critical given the straightforward read-only nature.

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 covers 100% of the parameters with adequate descriptions, so the baseline is 3. The tool description adds no extra meaning to the parameters (e.g., how 'days' interacts with 'over time'), but it doesn't need to since the schema already explains them sufficiently.

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 uses a specific verb+resource ('Gets traditional licensing usage statistics') and adds a concrete detail ('Shows robot counts by type over time') that makes its purpose unmistakable. It also distinguishes itself from siblings like uipath_get_consumption_license_stats via the 'traditional' qualifier.

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 clearly indicates the permission required and implies that it targets traditional licensing, giving context on when to use it. However, it does not explicitly name alternative tools or state when not to use this tool, so it lacks explicit exclusion guidance.

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