uipath_get_folders

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

With no annotations provided, the description carries the full burden of behavioral disclosure, but it only says 'Get folders,' which is essentially a restatement of the tool name. It does not disclose whether the operation is read-only, how pagination works (despite the skip/limit parameters), what data is returned, or any limitations like folder hierarchy or organizational units.

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, well-structured sentence of seven words with no wasted words or repetition. It is front-loaded with the action and resource, making it immediately clear what the tool does in minimal space.

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?

The tool is simple, but the description is too minimal to be complete. There is no output schema, so the description should explain what is returned (e.g., an array of folder objects), but it does not. It also lacks any mention of how folders are scoped, which is significant given the many sibling tools and the complexity of UiPath Orchestrator's folder model.

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 input schema already provides 100% coverage with descriptions for both parameters (skip and limit), so the baseline is 3. The description adds no additional meaning beyond the schema, but since the schema is complete, no further compensation is needed.

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 gets folders from UiPath Orchestrator, with a specific verb and resource. However, it does not distinguish this tool from the many other sibling get_* tools, such as uipath_get_queue_items or uipath_get_jobs, beyond the resource name.

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 no guidance on when to use this tool versus alternative tools, such as uipath_get_folder_overview or other folder-related operations. It also does not mention any prerequisites or context for using folders, such as the need for folder permissions or how folders relate to other UiPath entities.

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