ncloud_apigw_create_api_key

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

Annotations already declare destructiveHint=false. The description adds the dryRun feature for preview, which adds value beyond annotations. It clarifies the non-destructive creation behavior. However, it does not disclose other potential behaviors like authentication requirements or return format.

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?

Two sentences with no fluff. The first sentence states the purpose, and the second adds a specific usage hint. Every sentence is valuable and front-loaded.

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 creation tool with 1 required and 2 optional parameters, the description covers the core functionality and adds the dryRun preview feature. However, it does not mention the return value or what the created API key contains, which could be useful given no output schema.

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 description coverage is 100%, so the baseline is 3. The description mentions dryRun for preview, which aligns with its schema description. No additional meaning is added beyond what the schema already provides for the other parameters.

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 a new API key' and the resource 'in API Gateway'. It specifies the verb and resource, and among sibling tools like ncloud_apigw_list_api_keys and ncloud_apigw_delete_api_key, this tool is uniquely identified as the creation operation.

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 provides a usage hint for the dryRun parameter but does not explicitly guide when to use this tool versus alternatives. No mention of when not to use or comparison to list/delete operations. Usage is implied but not explicit.

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