local_ydb_list_versions

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

Annotations already indicate readOnlyHint, destructiveHint, idempotentHint, and openWorldHint. The description adds value by detailing sorting behavior, pagination bounds, and truncation reporting, which are beyond what annotations provide. No contradictions.

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 pack all essential information: first sentence states purpose and sorting, second gives usage guidance and pagination details. No extraneous words, front-loaded structure.

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?

With no output schema, the description mentions truncation reports but does not specify exact response format (e.g., list of tags). However, the tool name and context make it clear. The description is nearly complete for an agent to use 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 100%, so baseline is 3. The description adds extra context by explaining that pageSize and maxPages together 'bound registry pagination and the response reports truncation,' which clarifies their interplay beyond individual schema descriptions.

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 'List published registry tags for a local-ydb container image, with numeric version tags sorted newest first.' It specifies a specific verb and resource, and explicitly differentiates from sibling tools by noting its use before local_ydb_upgrade_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?

The description explicitly advises 'Use before local_ydb_upgrade_version to choose a target tag' and explains how to interpret pagination parameters (pageSize, maxPages) and the truncation report, providing clear when-to-use guidance.

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