ncloud_sourcebuild_list_compute

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

The description aligns with the readOnlyHint: true annotation by using 'List', which implies a safe, non-mutating operation. However, it adds no additional behavioral context such as return format, pagination, or any caveats. With the annotation already declaring read-only safety, a baseline score of 3 is appropriate.

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 sentence that immediately states the verb and target resource. It contains no unnecessary words and is well-structured for quick comprehension.

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 operation, the description sufficiently conveys the purpose. It does not describe the return values, but given the simplicity of the tool and the absence of an output schema, this is a minor gap. The description is otherwise complete enough for an agent to invoke the tool 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?

The input schema has zero parameters and 100% schema description coverage, so there are no parameter semantics for the description to clarify. The baseline score for a no-parameter tool is 4, as no further explanation is needed.

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 action ('List') and the specific resource ('available compute types for SourceBuild build environment'). This is specific enough to distinguish it from sibling SourceBuild list tools such as ncloud_sourcebuild_list_docker_engines or ncloud_sourcebuild_list_runtimes.

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 no guidance on when to use this tool versus alternatives. It is a simple, zero-parameter list operation, but the description does not explicitly state that it should be used to discover compute types before creating or updating a build project.

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