ncloud_datastream_create_topic

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

Annotations declare non-destructive (destructiveHint=false). Description adds dry-run preview capability and prefix requirement. Does not mention failure modes or quotas, but sufficient given 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?

Two sentences, no filler. First sentence states core purpose, second provides critical usage details. Every word earns its place.

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 no output schema, description covers creation purpose, prerequisites, and preview. Lacks post-creation response details, but agent can infer or use sibling tools. Adequate for complexity (5 params).

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 covers 100% of parameters with descriptions. Description adds valuable context: name must include prefix (not in schema hints) and reinforces dryRun's purpose, improving semantic clarity beyond schema alone.

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 ('Create'), the resource ('topic'), and the service ('Data Stream') with a specific verb. It distinguishes from siblings like list/update/delete by focusing on creation.

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 prerequisites: name must include account prefix and encourages dry-run for preview. Implicitly distinguishes from update/delete by context, but lacks explicit when-not-to-use guidance.

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