ncloud_datastream_get_registry_config

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

Annotations already declare readOnlyHint=true, and the description confirms a read operation via 'Get'. It does not add significant behavioral details beyond what annotations provide, such as error handling or authentication requirements, which is acceptable since annotations cover safety.

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 of 8 words, front-loaded with the action and resource, with no redundant information.

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 is minimal; it does not explain what the compatibility configuration entails, the return format, or potential edge cases. Given the tool's simplicity and lack of output schema, it is adequate but could be more informative.

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% with a single parameter (topicId) described as 'Topic ID'. The description does not add additional meaning beyond the schema, so baseline 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 'Get schema registry compatibility configuration for a Data Stream topic' clearly states the verb ('Get') and the specific resource ('schema registry compatibility configuration'), distinguishing it from siblings like ncloud_datastream_get_registry_info which retrieves broader registry information.

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 usage context by specifying the resource, but provides no explicit guidance on when to use this tool versus alternatives (e.g., ncloud_datastream_get_topic, ncloud_datastream_update_registry_config) or any prerequisites like topic existence.

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