ncloud_datastream_create_schema

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

The description does not disclose behavioral details beyond the annotation (destructiveHint: false). It doesn't mention schema validation, overwrite behavior, or whether changes take effect immediately. The annotation provides minimal safety info, and the description adds little further.

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, clear sentence with no fluff. It is appropriately sized for the tool's simplicity, though it could be slightly more structured by including key constraints.

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?

The description does not specify the expected output (e.g., schema details or success message), nor does it mention that the topic must exist. Given the lack of an output schema and minimal annotations, the description is incomplete for an agent to fully understand the tool's behavior and requirements.

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% from the input schema, so the baseline is 3. The description lists allowed types (AVRO, JSON, PROTOBUF) but this is already present in the schema enum. No additional meaning is added beyond what the schema provides.

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 ('schema for a Data Stream topic'), and enumerates allowed schema types (AVRO, JSON, PROTOBUF). It distinguishes this tool from sibling tools like list_schemas, get_schema, delete_schema, and check_schema_compatibility.

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 prerequisites (e.g., topic must exist) or when to use check_schema_compatibility first. The description lacks usage context.

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