local_ydb_list_versions

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

Annotations already indicate readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds value by disclosing registry pagination and authentication restrictions, and the sorting behavior, which are not in annotations or schema.

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 a single concise sentence that front-loads the core purpose, then adds usage context and pagination notes. No fluff, every clause contributes useful information.

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?

Given the annotations (read-only, idempotent) and 100% schema coverage, the description covers the key operational aspects: what it lists, sorting, usage before upgrade, and pagination limits. The tool is a read-only list operation; no output schema is present but the description adequately conveys the return behavior (sorted tags) without needing to detail the exact response structure.

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% with detailed descriptions for image, maxPages, and pageSize. The description mentions pageSize and maxPages bound pagination, reinforcing but not significantly extending the schema. It adds minimal additional semantic value beyond what the schema already provides, hence baseline 3.

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 lists published GHCR or Docker Hub tags for the local-ydb container image, with numeric versions sorted newest first. It specifies the resource (container registry tags), the action (list), and the sorting behavior, which fully distinguishes it from sibling tools like 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 says 'Use before local_ydb_upgrade_version', providing a clear when-to-use directive. It also mentions registry pagination and authentication restrictions, which implies the operational context and preconditions for the tool.

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