uipath_get_job_details

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

No annotations are provided, so the description carries the full burden. The verb 'Get' clearly indicates a read-only operation, and the description does not mislead. However, it does not disclose details like whether the operation is safe, what the response contains, or any potential side effects. The read-only nature is implied but not explicitly stated, so a score of 3 is appropriate.

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, front-loaded sentence that directly states the tool's purpose. There is zero wasted text; every word earns its place. It is appropriately sized for a simple lookup operation.

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?

With no output schema and no annotations, the description should explain what 'detailed information' includes, but it does not. It also does not clarify the role of the optional folderId parameter. The description is adequate for a basic get-by-ID tool but leaves gaps about the response shape and parameter interplay, so a middle score is suitable.

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 the schema already documents both jobId and folderId. The description mentions 'by its ID' which aligns with jobId, but it adds no additional nuance beyond the schema. Baseline of 3 is warranted because the schema does the heavy lifting.

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 verb 'Get', the resource 'job', and the scope 'by its ID'. It distinguishes from sibling tools like uipath_get_jobs (which likely lists jobs) and uipath_get_job_stats (which provides aggregated statistics), making it highly specific.

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 clear context: use when you have a specific job ID and need detailed information about that job. It does not explicitly name alternatives or exclusions, but the 'by its ID' phrase implies a targeted lookup as opposed to listing operations, which is adequate guidance.

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