ncloud_datastream_list_topics

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

The description does not disclose behaviors beyond the readOnlyHint annotation. It lacks details such as pagination, whether the list includes all topics in the region, or any limits. The annotation already indicates read-only, so the description adds minimal value.

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 sentence that efficiently states the tool's purpose. No unnecessary words, and it is front-loaded with the key action and resource.

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 lacks information about the return value (e.g., structure of topics) since there is no output schema. For a list operation, it should at least mention that it returns a list of topic objects. The optional parameters (sortBy, descending, searchText) are not referenced, leaving the agent to infer their purpose from the schema only.

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?

The input schema has 100% description coverage for all three optional parameters. The description does not add parameter information, so the baseline score of 3 is appropriate. The description's claim of 'list all topics' slightly conflicts with the presence of optional filters, but this is minor.

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 ('List') and the resource ('all topics') on a specific service ('Data Stream serverless streaming service'). It is specific and distinguishable from sibling tools like ncloud_datastream_get_topic.

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 on when to use this tool versus alternatives (e.g., ncloud_datastream_get_topic for a single topic, or other listing tools). No exclusions or prerequisites mentioned.

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