ncloud_sourcebuild_list_compute

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

Annotations already declare readOnlyHint=true, so the agent knows this is a safe read operation. The description confirms the listing behavior. No contradictions. However, it does not disclose any additional behavioral traits (e.g., whether it returns a list of strings or objects, or if any authentication is needed), but given the tool's simplicity, this is adequate.

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, short sentence (8 words) that conveys the essential purpose without any fluff. It is optimally concise and front-loaded.

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 tool has zero parameters and no output schema, the description is nearly complete. It could be slightly improved by hinting at the return format (e.g., 'Returns a list of compute type identifiers'), but this is not critical for a simple list tool with valid annotations.

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 tool has no parameters, so the baseline is 4. The description does not need to add parameter information, and it correctly omits any.

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 resource (available compute types) with a specific context (for SourceBuild build environment). It distinguishes itself from sibling list tools like 'ncloud_sourcebuild_list_os' and 'ncloud_sourcebuild_list_runtimes' by specifying 'compute types'.

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, nor does it mention any prerequisites or conditions. For a simple list tool, users would benefit from knowing that this tool is for listing compute types available for SourceBuild, but no usage context or exclusions are given.

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