ncloud_secret_get_secret

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

With readOnlyHint=true already declaring the safe-read profile, the description adds genuinely useful behavior: it enumerates what comes back (metadata, rotation settings, protection key) and, crucially, rules out the secret value itself, which is the first thing an agent might wrongly assume. It doesn't cover auth or error behavior, but that is minor against the annotation.

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 sentence with zero filler, front-loaded with the core action and ending on the disambiguating clause that matters most.

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 two-parameter read tool with a readOnly annotation and a fully documented schema, the description is nearly complete: it summarizes the return content even though no output schema exists. Only the absence of any note on permissions or failure modes keeps it from a full 5.

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%, so both secretId and the keyIsolation enum (global vs regional host selection) are fully documented in the schema. The description adds no parameter-level 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) and resource (secret details) and explicitly scopes it with 'not the value', which cleanly distinguishes it from the sibling ncloud_secret_get_secret_value and ncloud_secret_get_secret_stage_value. An agent can pick this tool without opening either schema.

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 'not the value' clause tells the agent when NOT to use this tool, implying the value-fetching siblings for that case, and the schema's reference to ncloud_secret_list_secrets shows how to obtain the ID first. It stops short of naming the alternative tool explicitly, so it is clear context rather than a full when/when-not routing rule.

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