vro_list_executions

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

readOnlyHint=true already tells the agent this is a safe read operation. The description adds useful return-field context (id, state, start/end, started by), which matters since no output schema exists, but it does not define 'recent', the default limit, or pagination behavior.

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?

A single front-loaded sentence with the verb and resource first and the returned fields in parentheses. No wasted words, though it is terse to the point of omitting operational detail.

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?

For a read-only list tool with annotations covering safety, the core purpose is conveyed. However, 'recent' is undefined, no default or maximum for limit is given, and there is no hint about how the state filter interacts with the results, which leaves real gaps for a filtering list operation.

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 coverage is 67%, and the description's parenthetical lists returned fields rather than inputs, so it adds no meaning for the three parameters. The 'limit' parameter has no schema description and no compensating explanation in the description, leaving the agent to guess its default and cap.

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?

States a specific verb (List) and resource (executions of a workflow), so the agent knows it retrieves execution history rather than running or fetching a single execution. It does not explicitly distinguish itself from the singular sibling vro_get_execution, but the intent is unambiguous.

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?

There is no when-to-use or when-not-to-use guidance, and no mention of alternatives such as vro_get_execution for a single run or vro_run_workflow to start one. The agent must infer the list-vs-get distinction from the name alone.

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