invariance_workflow_list

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safe read-only nature is established without needing the description. The description adds the useful detail that results are workflow definitions with schema-like fields, but it does not disclose pagination, ordering, or whether the full definition objects are returned. This is acceptable given the zero-parameter scope.

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 a colon-delimited list of what the definitions contain. There is no filler, repetition, or unnecessary detail; every word earns its place.

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 zero-parameter list operation with read-only annotations, the description is nearly sufficient. It names the resource type and its relevant contents. It could slightly improve by clarifying whether it returns summaries versus full definitions, but the sibling tools and the description together make the callable intent clear.

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 tool has zero parameters, so the baseline is 4. The description's mention of typed fields, expected steps, allowed outcomes, and custom metrics gives context about what the returned definitions contain, which indirectly informs callers what to expect even though no parameters need explanation.

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 ('List workflow definitions') and enumerates the meaningful contents: typed fields, expected steps, allowed outcomes, and custom metrics. This clearly differentiates it from sibling tools like invariance_workflow_get, invariance_workflow_create, and invariance_workflow_observability_list.

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 gives no explicit guidance on when to use this tool versus alternatives such as invariance_workflow_get or invariance_workflow_observability_list. The word 'list' implies enumeration, but there is no when-to-use, when-not-to-use, or mention of alternative tools.

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