ncloud_datastream_create_connector

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

Annotations only provide destructiveHint=false. The description adds the behavioral constraint 'Only one connector per topic' and hints at dry-run capabilities. It does not contradict annotations. For a create tool, it could disclose more about idempotency or asynchronous behavior, but the added constraint is useful.

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 with two sentences, each providing essential information: what the tool does and a key usage tip. No wasted words 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?

While concise, the description omits prerequisites (e.g., topic existence, valid roleNrn) and does not mention potential asynchronous creation or response format. Given 12 parameters and no output schema, a bit more context would improve completeness.

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 fully documents parameters. The description adds minimal value beyond schema: it notes 'Object Storage sink' (confirming purpose) and mentions dryRun usage. Baseline 3 is appropriate as the description does not significantly enhance parameter understanding.

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 'Create a connector (Object Storage sink) for a Data Stream topic' with a specific verb (create) and resource (connector). It also adds the constraint 'Only one connector per topic', which distinguishes it from sibling tools like update or delete connectors.

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 provides clear usage context: it creates an Object Storage sink connector for a topic. The tip 'Use dryRun=true to preview' guides safe usage, and the one-per-topic constraint implies when to use alternatives (update/delete). However, it does not explicitly state when not to use or direct to specific sibling tools.

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