uipath_get_dashboard_summary

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. It only states what the tool does without mentioning any behavioral traits such as required permissions, return format, potential errors, or the fact that it is a read-only operation. This lack of context leaves the agent uncertain about side effects or prerequisites.

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 one concise sentence that is front-loaded with the primary purpose. It contains no filler and is appropriately sized for the simple tool, though it is brief.

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 has no annotations and no output schema, yet the description fails to explain what the dashboard summary contains beyond 'queue and job statistics' or what the return value looks like. Given the complexity of aggregating multiple data sources, the description is incomplete for an agent to anticipate the tool's output or behavior.

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 schema has 100% description coverage for the single parameter folderId, which is described as 'Folder ID to get dashboard summary for.' The description adds no extra parameter meaning, but the schema already fully documents it, so a baseline score of 3 is appropriate.

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 it 'Get a comprehensive dashboard summary with queue and job statistics,' identifying the resource (dashboard summary) and the included data (queue and job statistics). It is specific enough to distinguish from sibling tools that focus on individual queue or job stats, though it could more explicitly emphasize the aggregated nature.

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 the many sibling tools that provide queue stats, job stats, or other specific metrics. There is no mention of preferred use cases, alternatives, or exclusions.

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