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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds a useful scope constraint ("only reads tenant versions"), but says nothing about ordering, pagination, or what version metadata comes back. Beyond the tenant-scoping note it mostly restates the read-only nature already in annotations.

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?

Short and front-loaded: purpose first, then usage, then limits, then example. The telegraphic fragments ("Limits:", "Next step:") read as notes rather than prose but each sentence earns its place. The example is somewhat redundant given a single well-documented string parameter.

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 one-parameter, read-only listing tool with full annotation coverage and no output schema, the description covers purpose, routing, scope limits and a next step. The only real gap is what a returned version looks like, which matters because the stated use case is finding the active version.

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?

With a single parameter at 100% schema description coverage, the schema already carries the semantics. The inline example {"workflowId":"invoice-flow"} gives a small concrete assist but adds no format or sourcing detail beyond what the schema provides. Baseline 3 applies.

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?

"List the versions of one workflow" gives a specific verb and resource, and the qualifier "of one workflow" implicitly scopes it against the global workflow_versions_list sibling. It stops short of naming that sibling explicitly, so an agent choosing between the two still has to infer the distinction.

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?

Provides a concrete when-to-use ("need the active version before an edit") and an explicit when-not ("need to activate a version"), plus a forward pointer to workflow_apply_edits. It does not name the tool that handles activation or distinguish itself from workflow_versions_list, which leaves the exclusion incomplete.

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