ncloud_sourcecommit_delete_repo

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

The description adds value beyond the destructiveHint annotation by explicitly stating the operation is permanent and requires confirm=true to execute. This informs the agent of the irreversible nature and safety mechanism, which is useful context not present in structured fields.

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, concise sentence with a clear warning prefix and essential instruction. Every word contributes meaning—no filler 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?

For a simple destructive operation with two parameters and no output schema, the description covers the key facts: action, permanence, and the required confirm flag. It does not explain what happens when confirm is false, but this is inferable from the schema's default false value. Overall, adequate for the tool's complexity.

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 schema already fully documents both parameters. The description's mention of confirm=true restates the schema's own parameter description without adding new syntax, formatting, or constraints, so it meets the baseline but adds no extra semantic value.

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 states a specific action ('Permanently delete') on a specific resource ('SourceCommit repository'), making the purpose clear. However, it does not explicitly distinguish from the sibling tool ncloud_sourcecommit_delete_repo_by_id, which likely deletes by repository ID rather than name.

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?

No guidance is provided on when to use this tool versus alternatives, such as ncloud_sourcecommit_delete_repo_by_id. The only instruction is 'Set confirm=true to execute,' which is a parameter-level requirement rather than usage context or exclusions.

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