ncloud_ncr_get_image

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

Annotations already declare readOnlyHint=true, so the safety profile is covered, and the description confirms the read nature by embedding 'GET /repositories/{registry}/{imageName}'. However, it adds nothing about authentication, scoping, or error behavior beyond the endpoint path, so the added value is modest.

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 front-loaded sentence with the core purpose first and the REST endpoint as supporting detail. No filler, though the parenthetical path is slightly redundant given the parameter names.

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 simple two-parameter read tool with full schema coverage and annotations, the description is minimally sufficient. It leaves the return payload undocumented and provides no guidance on when this detail view is preferable to the sibling list/tag tools, so gaps remain but are not severe.

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 description coverage is 100% and both parameters (registryName, imageName) are documented in the schema, including the URI-encoding note for imageName. The description contributes no additional parameter meaning, so the baseline 3 applies.

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?

States a specific verb ('Get detailed information') and resource ('a specific container image'), so the operation is unambiguous. It does not distinguish itself from close siblings like ncloud_ncr_get_tag_detail or ncloud_ncr_list_images, which a single clause could have done.

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?

There is no when-to-use guidance, no mention of prerequisites (e.g. needing an existing registry/image), and no routing to alternatives such as list_images for enumeration or get_tag_detail for tag-level data. Usage is only implied by the name.

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