list_processes

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

No annotations are provided, so the description bears full responsibility for behavioral disclosure. It only indicates that the tool is scoped to the current folder, but it fails to mention that the operation is a read-only query, what the response format looks like, or any pagination behavior. More context is needed for safe agent invocation.

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 brief (two lines + docstring) but omits important information. It is not overly verbose, yet it sacrifices completeness for brevity. A balanced structure would include both conciseness and essential details.

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 (1 optional param, no output schema, no annotations), the description should at least explain the return value and any implicit behavior. It only states the resource and folder scope, leaving agents to guess about the output format, filtering, or error conditions.

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 has 0% description coverage, so the description must compensate. It adds meaning for the 'top' parameter: 'Optional maximum number of items to return.' This clarifies the parameter's role beyond the schema's type-only definition. However, no additional parameter details (e.g., default behavior, constraints) are provided, making the addition adequate but not exceptional.

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 purpose: 'List UiPath processes (Releases) available in the current folder.' It uses a specific verb ('list') and resource ('processes (Releases)') and adds scope context ('current folder'), distinguishing it from sibling tools that are unrelated (e.g., start_job, add_queue_item).

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 alternatives, no prerequisites, and no when-not-to-use instructions. It simply lists the available parameter, ignoring the need to help agents decide between list_processes and other list-* tools.

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