ncloud_create_custom_schema

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

Annotations already indicate destructiveHint=false, so the non-destructive nature is clear. The description adds minimal behavioral context, such as the purpose ('for custom metrics'), but does not disclose what happens on conflict (e.g., duplicate schema), idempotency, or required permissions. More transparency is needed for a creation tool.

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 sentence, 14 words, which is highly concise and front-loaded with the key action. However, it could be slightly restructured to include usage context without much additional length.

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 (3 parameters, no output schema, creation use case), the description is incomplete. It lacks information expected outputs (e.g., schema ID), prerequisites (e.g., existing product or permissions), and potential error conditions. The agent may not have enough context to confidently invoke this tool.

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 has 100% coverage with descriptions for all parameters. The description adds no additional meaning beyond what the schema provides. For example, it does not explain how 'prodName' relates to existing products or the purpose of 'fields' in the context of Cloud Insight. Baseline score of 3 is appropriate since the schema does the heavy lifting.

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 ('Create') and the resource ('user-defined custom schema in Cloud Insight for custom metrics'). It specifies a distinct resource from siblings like ncloud_update_product_schema or ncloud_delete_product_schema. However, it could be more explicit about how it differs from ncloud_create_custom_resource, which might be related.

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 when-to-use or when-not-to-use guidance is provided. The description does not mention prerequisites, alternatives (e.g., using ncloud_update_product_schema for modifications), or context where this tool should be chosen over others.

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