uipath_get_sessions

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

With no annotations, the description carries the burden of behavioral disclosure. It reveals that the tool lists active sessions and their states, including Available, Busy, and Disconnected. This goes beyond a plain 'get sessions' and informs the user about the included states, though it does not elaborate on pagination or auth requirements.

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 core action, and contains zero filler. Every phrase earns its place.

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?

Given the tool's simplicity (no output schema, all parameters optional) and the detailed schema, the description is sufficiently complete. It clarifies the domain and the output's meaning (robot states). It does not mention pagination, but the skip and limit parameters already cover that indirectly.

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 parameters are well described in the schema. The description adds minimal extra meaning, but it does align the 'state' filter with the states listed in the description, reinforcing the semantics. This matches the baseline for high schema coverage.

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 the tool's function: retrieving active robot sessions from UiPath Orchestrator and showing connected robots with their current state. It differentiates from sibling tools like get_robots or get_machines by focusing on sessions and runtime states.

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 (to see which robots are connected and their state), but it does not explicitly compare with alternatives or state when not to use it. No exclusions or alternative tool names are mentioned, 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.