ncloud_pca_delete_ocsp

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

The description adds value beyond the annotations (destructiveHint, idempotentHint) by explicitly stating the destructive consequence ('remove the OCSP URL from all certificates') and the safety mechanism (confirm flag). No contradictions with annotations.

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, front-loaded sentence with a warning symbol. Every word adds value—no fluff or redundancy.

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?

The description covers the destructive nature and confirm flag but omits details about return value, behavior when confirm=false, and error conditions. Given no output schema, more context on what to expect after invocation would be helpful.

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%, so the schema already describes both parameters. The description reiterates the confirm parameter's purpose ('Set confirm=true to execute') but does not add new meaning beyond the schema. Baseline 3 is appropriate.

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 'Delete OCSP configuration' and the resource, and distinguishes it from sibling PCA tools (e.g., create_ocsp, get_ca). The verb 'delete' and specific resource 'OCSP configuration' are precise.

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 mentions the confirm flag requirement ('Set confirm=true to execute') but does not provide explicit guidance on when to use this tool versus alternatives like updating OCSP or when not to use it. No prerequisites or exclusions are stated.

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