list_application_versions

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

With no annotations, the description carries full responsibility for behavioral disclosure. It explains the versioning mechanism and provides detailed return structure. However, it does not explicitly state whether the operation is read-only, requires authentication, or has no side effects. The verb 'List' implies read-only, but this is not made explicit.

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?

The description is well-organized with an intro, usage note, and structured Args/Returns sections. It is informative without excessive length, and every section adds value.

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?

The description covers the main purpose, provides background on version recording, and gives a comprehensive Returns section. It also references the companion tool for setting latest version. For a simple list operation with one parameter and an existing output schema, this is fairly complete.

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 description includes an Args section that explains the application_name parameter as 'Name of the DBOS application', providing some meaning beyond the raw schema. Given only one parameter and 0% schema coverage, this is sufficient, though the description could add more context about allowed values or format.

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 clearly states the tool's function: 'List all versions of an application from DBOS Conductor.' This is a specific verb and resource, and it differentiates from sibling tools like list_applications and set_latest_application_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?

It provides context about when versions are recorded and explicitly points to set_latest_application_version for controlling the current version, which indirectly guides selection. However, it does not explicitly state when to use this tool over list_applications or other siblings.

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