ncloud_cm2_deactivate_eab_credential

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

Annotations only carry destructiveHint=true, but the description discloses far more: the downstream impact on ACME clients, the confirm gate, the public-zone restriction, and an auth failure mode (Sub Account keys rejected with HTTP 403). This is exactly the kind of behavioral context an agent needs before invoking a destructive 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?

Dense but front-loaded: the destructive warning and effect lead, followed by execution, scope, and auth constraints. The trailing provenance parenthetical ('confirmed by Ncloud support; verified 2026-10-02 with NCP_ADMINISTRATOR') is somewhat verbose for an agent but adds trust value rather than fluff.

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 destructive two-parameter tool with no output schema, the description covers everything needed to call it correctly: effect, confirmation requirement, zone scope, and credential requirements. Nothing critical is left for the agent to infer.

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 both parameters (confirm, accountId) are already documented in the schema. The description's 'Set confirm=true to execute' only restates the schema's confirm semantics and adds no new meaning, so baseline 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?

States a specific verb ('Deactivate') and resource ('ACME EAB credential') plus the concrete consequence (ACME clients stop working). This distinguishes it cleanly from siblings like ncloud_cm2_create_eab_credential and ncloud_cm2_list_eab_credentials without opening either schema.

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?

Gives clear conditions: set confirm=true to execute, public-zone only, and requires a main-account API key. It does not explicitly name an alternative or say when not to use it, but the scope and permission constraints strongly imply the valid context.

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