ncloud_sourcebuild_list_docker_engines

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

The readOnlyHint annotation already establishes this as a safe read operation. The description adds only the word 'available', which is largely implied by 'List', and does not disclose output format, pagination, or other behavioral details. This is acceptable given the annotation coverage.

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 entire description is a single sentence that begins with the verb 'List' and contains no filler. Every word contributes meaning, making it highly concise and well-structured for a simple operation.

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?

For a zero-parameter, read-only list tool, the description fully covers what the tool returns (Docker engine versions) and the scope (SourceBuild). No output schema is present, but the purpose is simple enough that no additional context is required.

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 input schema has zero properties, and the description correctly implies that no parameters are needed. With no parameters to explain, the baseline of 4 applies, and the description adds no unnecessary parameter detail.

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 uses the specific verb 'List' and identifies the resource as 'Docker engine versions for SourceBuild', which exactly matches the tool name. This clearly differentiates it from sibling tools like ncloud_sourcebuild_list_runtimes or ncloud_sourcebuild_list_os.

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?

No guidance is provided about when to use this tool versus alternatives. There are no scenarios, exclusions, or comparisons with sibling list tools such as ncloud_sourcebuild_list_runtime_versions, so the agent has no basis for choosing among similar list operations.

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