local_ydb_check_prerequisites

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

Annotations indicate idempotent and non-destructive. The description adds critical behavioral details: it never installs Docker, and may install curl/ruby with confirm. No contradictions with 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?

Two concise sentences: first states purpose, second explains the dual mode. No fluff or repetition. Front-loaded with key 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?

The description adequately covers what the tool checks and the two modes. Input params are well documented. No output schema, but the description hints at the return content. Could be improved by explicitly listing return fields or possible errors, but it is sufficient.

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 covers all three parameters with descriptions. The tool description adds value by explaining the effect of the confirm parameter, which goes beyond the schema description. Baseline 3 is raised to 4 due to this additional context.

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 checks target-host prerequisites for Docker, curl, ruby, and the rootPasswordFile. It distinguishes two modes (plan-only and confirm) and is distinct from sibling tools, which focus on other operations like adding nodes or storage.

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 explains the behavior in plan vs. execute mode and notes that Docker is never installed. However, it does not explicitly state when this tool should be used relative to others, such as before bootstrap or node additions, though the name implies it.

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