ncloud_sourcebuild_list_registries

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

The annotation readOnlyHint=true already communicates the safe, non-mutating nature. The description adds the scope 'available for SourceBuild', which is useful context, but it does not disclose any other behavioral aspects such as pagination, return format, or the fact that it likely queries the NCR service.

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?

A single, well-structured sentence that immediately conveys the purpose. No filler, redundant information, or unnecessary details. It earns its place perfectly.

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 parameterless list tool with a read-only annotation and no output schema, the description provides sufficient information. It clearly states what is listed and the filter ('available for SourceBuild'). A minor gap is not explaining the relationship to NCR registries, but the sibling tools and naming conventions make this inferable.

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 zero parameters, so there is no burden on the description to explain parameter semantics. The description correctly avoids inventing parameters and remains focused on the tool's core function.

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 resource ('Container Registry registries available for SourceBuild'). The 'available for SourceBuild' qualifier distinguishes it from the similar sibling tool ncloud_ncr_list_registries, which lists all registries without that filter.

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 clearly conveys the context: it is for listing registries that are available to SourceBuild. However, it does not explicitly mention when not to use it or name alternatives like ncloud_ncr_list_registries. The context is clear enough for an agent to infer the appropriate use case.

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