list_workflow_versions

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

Describes that it lists versions with timestamps and the Consumption SKU constraint. No annotations provided, so description carries burden; it is adequate but lacks details on permissions, error handling, or response format.

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?

Two sentences, no waste, front-loaded with key information: action, resource, and SKU limitation.

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 simple list tool with 4 parameters and no output schema, the description is fairly complete: includes resource type, data returned, and constraint. Missing default ordering or pagination info, but acceptable.

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 100%, so baseline 3. Description does not add extra meaning beyond schema; e.g., 'top' parameter not explained further.

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?

Clearly states it lists all versions of a Consumption Logic App workflow with creation and change times, distinguishing from siblings like list_workflows and get_workflow_version.

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?

Explicitly states 'Only available for Consumption SKU,' setting a clear usage condition. Could mention alternatives for Standard SKU, but the constraint is clear.

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