ncloud_hadoop_get_notebook_detail

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

The annotation readOnlyHint=true already indicates a safe read operation, and the description aligns with a read-only 'get' action. However, the description does not disclose what specific details are returned, whether any additional inputs are required (like region), or any other behavioral nuances, so it adds minimal context beyond 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?

The description is a single concise sentence that is front-loaded with the verb and resource. There is no redundant or extraneous wording, making it highly scannable.

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 read-only detail tool with complete parameter schema and a read-only annotation, this description is adequate but minimal. There is no output schema, and the description does not specify what 'detailed information' includes or whether the region code affects the result, leaving some ambiguity for an agent.

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 input schema covers 100% of parameters with descriptions ('Region code' and 'Notebook instance number'), so the baseline is 3. The description adds no additional parameter semantics, such as the format of the instance number or the optionality of region.

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 the specific verb 'get' and identifies the resource as 'a specific Cloud Hadoop notebook', which clearly distinguishes it from listing or creating notebooks. However, it does not explicitly contrast itself with sibling tools like list_notebooks, though the 'specific' qualifier implies a single-resource lookup.

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: the tool is for retrieving details of a particular notebook, presumably when its instance number is known. There is no explicit guidance on when to use this versus other notebook-related tools, nor any exclusions or prerequisites.

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