local_ydb_list_versions

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

Beyond annotations (readOnlyHint, idempotentHint, etc.), the description adds specific behavior: numeric version tags sorted newest first, pagination with pageSize and maxPages, and truncation reporting. This gives useful behavioral detail.

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 concisely convey purpose, sorting, usage context, and parameter behavior with no redundancy or unnecessary words.

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 sorting, pagination, and truncation reporting. However, it does not describe the response format (e.g., list of strings), which is absent from the output schema. Minor gap for a list operation.

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 schema covers all parameters with full description coverage. The description reinforces the role of pageSize and maxPages in pagination, but does not add new semantic detail beyond the schema defaults and limits.

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 registry tags for a local-ydb container image with numeric version tags sorted newest first, and explicitly mentions its role as a precursor to local_ydb_upgrade_version. This distinguishes it from sibling tools.

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 provides explicit guidance: 'Use before local_ydb_upgrade_version to choose a target tag'. It also explains how pagination parameters pageSize and maxPages bound the operation.

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