ncloud_ncr_get_registry

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

Annotations already declare readOnlyHint=true, so the safety profile is covered. The description adds genuine behavioral context the structured fields cannot: the underlying endpoint is absent from the official guide and the tool is 'kept pending live verification', warning the agent that results may be unreliable. It does not mention auth or rate limits, but the verification caveat is a meaningful, non-redundant disclosure.

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?

One sentence with a front-loaded purpose and a compact parenthetical caveat; nothing is wasted. The parenthetical is slightly awkward but carries real information rather than filler.

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 read-only single-parameter getter with no output schema, the description is nearly sufficient: it covers purpose plus the important reliability caveat. It would be stronger with a note on what 'detailed information' contains or how it differs from list_registries, but nothing critical is missing for correct invocation.

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 the single parameter (registryName) is fully documented in the schema, so the baseline is 3. The description adds no format, naming, or validation hints beyond what the schema already provides.

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 registry), making it clearly distinct from the list/create/delete siblings. Lacks any explicit contrast with ncloud_ncr_list_registries, but the singular-vs-plural and 'detailed' wording makes the intent inferable.

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 explicit when-to-use or when-not-to-use statement and no named alternative. The agent must infer that this is the detail view for a single registry versus ncloud_ncr_list_registries, and nothing tells it about prerequisites or likely failure modes beyond the parenthetical caveat.

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