uipath_get_assets

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

No annotations are provided, so the description must carry the full burden. The description only says 'List' which implies a read operation, but it does not explicitly state that the tool is read-only, that it may return sensitive credentials, or that results are paginated via skip/limit. This lack of behavioral detail is a significant gap.

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 that immediately state the action and resource. Every word earns its place, and there is no redundant or vague filler.

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 with three optional parameters and no output schema. The description plus schema give a basic understanding, but it lacks guidance on what happens if folderId is omitted, how pagination works, and what the return structure looks like. It is minimally viable but leaves gaps for an agent selecting and invoking the tool.

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 covers all three parameters (skip, limit, folderId) with descriptions, so baseline is 3. The description adds no additional parameter context, and even slightly conflicts with the pagination semantics by saying 'List all assets' while skip/limit control the result set.

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: 'List all assets in a UiPath Orchestrator folder.' The verb 'List' and resource 'assets in a folder' are specific, and the second sentence explains what assets are, helping distinguish this from sibling tools like uipath_get_queue_items or uipath_get_jobs.

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 context by explaining that assets store configuration values and credentials, implying when this tool is useful. However, it does not explicitly mention alternatives or exclusions, such as using uipath_get_robot_asset for robot-specific assets, so it stops short of a 5.

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