ncloud_cm2_revoke_certificate

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

Annotations already flag destructiveHint, but the description goes further: it explains the confirm=true gate, the wildcard behavior of certificateNo=0, the public-zone restriction, and a concrete auth failure mode (sub-account 403 verified with support). This is exactly the extra behavioral context annotations cannot carry.

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?

Front-loads the destructive warning and key mechanics in tight sentences. The trailing parenthetical about support verification and date is slightly verbose and doesn't help invocation, but overall it is well structured and earns most of its 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?

For a destructive mutation with no output schema, the description covers the confirmation gate, scope of revocation, zone restriction, and auth constraints — everything an agent needs to call it correctly.

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 all four params are already documented in the schema (including confirm, orderId, revokeType enum, and certificateNo=0). The description reinforces the certificateNo=0 case but adds no syntax or format detail beyond the schema, so the 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 (Revoke) and resource (Advanced certificate in Certificate Manager 2.0), and adds the important scope nuance that certificateNo=0 revokes the whole order. An agent can distinguish this from siblings like ncloud_cm2_reissue_certificate or ncloud_cm2_download_certificate.

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 concrete prerequisites: public zone only, main-account API key required, confirm=true needed to execute, and notes sub-account keys get HTTP 403. It stops short of naming alternative tools (e.g., reissue vs revoke) or when-not-to-revoke, but the operational context is clear.

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