ncloud_get_init_script_detail

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

The readOnlyHint annotation already indicates a safe read operation, so the description only needs to add additional context. However, it adds none beyond restating the tool's purpose—no information about return format, error behavior, or any constraints. The description is consistent with the annotation but provides no extra transparency.

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 concise sentence that front-loads the verb and resource, with no filler or repetitive content. It is appropriately sized for the tool's simplicity.

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?

With one required parameter, readOnlyHint annotation, and no output schema, the description is minimally adequate. However, it does not indicate what 'detailed information' includes (e.g., script name, creation time, content), which could help the agent anticipate the response. For such a simple tool, this is a minor gap.

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 coverage is 100% with the single parameter initScriptNo described as 'Init script number to query'. The description adds no additional parameter semantics, but the baseline of 3 is appropriate when the schema fully documents the parameter.

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 uses a specific verb ('Get') and resource ('detailed information about a specific init script'), clearly distinguishing it from listing all init scripts or creating/deleting one. This matches the pattern of sibling tools like ncloud_list_init_scripts and ncloud_create_init_script.

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?

Usage is implied by the word 'specific' and the contrast with sibling 'list_init_scripts', but the description does not explicitly state when to use this tool over list/create/delete alternatives. No exclusions or prerequisites are mentioned.

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