ncloud_apigw_delete_api_key

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

Annotations already indicate destructiveHint=true and idempotentHint=true. The description adds value by explicitly stating 'Destructive' and 'Permanently delete', and explains the confirm parameter's role as a safety mechanism. It does not discuss idempotency or error cases, but the key behavioral trait (destructive) is well communicated.

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?

A single sentence with a warning emoji conveys all essential information. No superfluous text, and the most critical info (destructive nature and confirm flag) is 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 simple delete operation with full schema coverage and annotations, the description is sufficient. It explains the destructive action and the confirmation requirement. Missing details like return value are not critical given the tool's simplicity.

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% with both parameters described. The description reinforces the confirm parameter's purpose but does not add significant meaning beyond the schema. The apiKeyId parameter's meaning is clear from its name and schema description.

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 tool's verb ('delete') and resource ('API key from API Gateway'), and the 'Permanently delete' indicates it's a permanent action. It distinguishes from sibling tools focused on other services or operations.

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 explicitly states the requirement to set confirm=true to execute, which acts as a usage guideline. However, it does not discuss when to use this tool versus alternatives like create_api_key or list_api_keys, but for a delete operation the context is clear.

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