vro_workflow_get_all

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is fully covered without the description. The description adds nothing beyond that — it does not disclose pagination semantics, default page size, whether the list is scoped to a tenant/organization, or what the response envelope looks like.

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?

It is short and front-loaded, but the second line is a raw HTTP path that merely duplicates the annotation title, so one of two sentences carries no incremental information. Not verbose, just partly wasted.

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 list tool with a nested required parameter object, no output schema, and 0% schema coverage, an agent still lacks pagination behavior, default sizing, sort syntax, and response shape. Annotations cover safety but not the operational details needed to call it correctly.

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 0% and the description says nothing about any parameter. The nested required `page` object (page.page, page.size, page.sort) is genuinely ambiguous and would benefit from explanation, as would the `expand` flag, but the description offers no clarification beyond self-describing field names.

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 names a specific verb and resource ("Get a list of workflows"), so the agent knows exactly what the tool returns. It does not, however, distinguish itself from near-siblings such as vro_workflow_get_aggregated or vro_workflow_get_aggregated_one, so the agent must guess which listing endpoint is intended.

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 statement of when this list endpoint should be used versus vro_workflow_get_one or the aggregated variants, and no prerequisites or exclusions are given. The only guidance is the raw path "GET /vro/workflows", which restates the operation rather than advising usage.

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