ncloud_datastream_delete_topic

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

Adds context beyond annotations: messages will be lost, and confirm flag is required. Annotations already indicate destructive and idempotent, so description reinforces and specifies these details.

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?

Two sentences, no fluff. Uses warning emoji and front-loads key destructive nature and action required. Every sentence adds value.

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?

Complete for a delete operation: covers purpose, destruction, parameter usage, and safety requirement. No output schema expected, so return value omission is acceptable.

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%, and description adds meaning by explaining the confirm parameter's role as a safety gate and the topicId parameter's purpose. This helps the agent understand critical parameters.

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?

Clearly states 'permanently delete a Data Stream topic' with verb and resource. Distinct from sibling tools like create or update by explicitly being a deletion operation.

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?

Provides explicit instruction to set confirm=true to execute, which guides safe usage. Does not explicitly state when not to use, but the destructive warning implies caution.

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