ncloud_sourcecommit_delete_repo_by_id

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

Annotations already declare destructiveHint: true and idempotentHint: true. The description reinforces the destructive nature with a warning emoji and adds the confirm flag requirement. However, it does not disclose other behavioral details such as side effects on associated resources or permission requirements. The idempotentHint annotation may be contradictory given the destructive nature.

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 extremely concise and front-loaded with a clear warning and the essential usage instruction. Every sentence adds value without 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?

Given the simplicity of the operation (delete by ID) and no output schema, the description covers the core functionality and key safety requirement. However, it could be slightly improved by differentiating from the sibling delete tool and mentioning if the operation is reversible.

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?

Input schema coverage is 100% and includes parameter descriptions. The description reiterates the confirm flag's purpose but adds no new meaning beyond the schema. For repositoryId, it adds no additional context beyond the schema's 'Repository ID to delete'.

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 'Permanently delete a SourceCommit repository by ID', specifying the action (delete), resource (repository), and identifier type (ID), which distinguishes it from sibling tools like ncloud_sourcecommit_delete_repo that may use different identifiers.

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?

While the description provides the necessary usage instruction 'Set confirm=true to execute', it does not explicitly guide when to use this tool versus alternatives (e.g., ncloud_sourcecommit_delete_repo) or mention prerequisites or conditions.

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