ncloud_hadoop_get_notebook_detail

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

The annotation readOnlyHint already signals the tool is safe to use. The description adds that it returns detailed information, but does not disclose any other behavioral traits such as potential error conditions, authorization requirements, or response size. With annotations present, the description provides minimal additional value.

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 with no extraneous words. It is well-structured but could be slightly more informative without losing conciseness.

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 detail-get tool, the description is adequate but incomplete. It does not indicate what fields or sections of 'detailed information' are returned, and there is no output schema to compensate. The description does not guide the agent on how to interpret the response.

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% and both parameters have descriptions in the schema ('Region code', 'Notebook instance number'). The description does not add any new meaning beyond what the schema already provides, so the baseline score of 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?

The description clearly states the action ('get') and the resource ('detailed information about a specific Cloud Hadoop notebook'), making the tool's purpose unambiguous. It implicitly distinguishes from sibling list tools by specifying 'specific', though it could explicitly mention alternatives.

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 guidance is provided on when to use this tool versus alternatives like ncloud_hadoop_list_notebooks or ncloud_hadoop_create_notebook. There is no mention of prerequisites such as needing a notebook instance number from a list operation.

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