ncloud_hadoop_create_notebook

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

Beyond the annotation (destructiveHint=false), the description only adds the prerequisite of an existing cluster. It does not disclose that creation may take time, incur costs, or require specific cluster states. With annotations present, the bar is lower, but the description offers minimal additional behavioral context.

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, front-loaded sentence with no fluff. Every word earns its place, conveying the core action and attachment constraint efficiently.

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?

Given the tool's complexity (13 params, 6 required, no output schema), the description is thin. It provides the essential context but omits prerequisite details like the cluster must be in a certain state, the bucket must exist, or what the response contains. Schema covers params, but the description doesn't tie them together.

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% for all 13 parameters, so the schema already explains each parameter. The description adds no parameter-level meaning or relationships (e.g., the dependency on useNotebookBlockStorage). Baseline 3 is appropriate.

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 'Create' with a clear resource 'Cloud Hadoop notebook instance' and adds a key qualifier 'attached to an existing cluster'. This clearly distinguishes it from sibling tools like ncloud_hadoop_delete_notebook or ncloud_hadoop_list_notebooks.

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 description implies the tool is for creating a notebook on an existing cluster, which gives context but no explicit alternatives or when-not-to-use guidance. It doesn't reference sibling tools or exclusion criteria, so it's not fully instructive.

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