ncloud_datastream_get_registry_info

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

Annotations already declare readOnlyHint=true, so the description's claim of retrieving info is consistent. However, the description adds no additional behavioral context beyond what the annotation provides (e.g., error handling, idempotency, or data freshness).

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, concise sentence (12 words) that front-loads the key information. Every word is necessary and contributes to understanding the tool's purpose.

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 the tool's simplicity (one parameter, no output schema), the description sufficiently conveys what the tool returns (endpoint and modifiability info). It could be more complete by mentioning idempotency or typical use cases, but it is adequate for a straightforward read operation.

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 single parameter 'topicId' is fully described in the input schema with a description of 'Topic ID'. The tool description adds no extra meaning or constraints beyond the schema, which has 100% coverage. Baseline score 3 applies.

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 specifies the action ('Get') and the resource ('schema registry endpoint and modifiability info for a Data Stream topic'). It uses a specific verb+resource pattern and distinguishes from sibling tools like ncloud_datastream_get_topic, which retrieves topic details, not registry-specific info.

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 implies the tool is used when you need registry info for a specific topic, but it provides no explicit guidance on when to use this tool versus alternatives (e.g., ncloud_datastream_get_registry_config). No 'when to use' or 'when not to use' advice is given.

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