ncloud_get_schema_keys

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

The annotation readOnlyHint=true already signals a safe read operation, so the description does not need to repeat that. The description adds a small amount of context by specifying the data source ('available in Cloud Insight') and the exact item being listed (cw_key). However, it does not disclose what the returned list contains, whether it can be empty, or any other behavioral details beyond the annotation.

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, well-structured sentence that front-loads the action ('Get the list') and follows with the specific object. There is zero wasted language, and every word adds value.

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 low complexity (no parameters, no output schema), the description is sufficient to understand its purpose and output. It does not explain what cw_key is or how the list is ordered, but such details are unnecessary for this simple read-only retrieval.

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 tool has zero parameters, so the description does not need to explain any input fields. The schema is empty with 100% coverage, and the description adds meaningful context about the output (the cw_key list). This meets the baseline for parameterless tools.

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 tool's function: retrieving a list of system schema product keys (cw_key) available in Cloud Insight. The verb 'Get' combined with the specific resource 'system schema product keys' makes the purpose unambiguous. However, it does not differentiate from sibling tools that also retrieve lists or keys, so it misses the top score.

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?

There is no guidance on when to use this tool versus alternatives. The description does not mention exclusions, prerequisites, or related tools, leaving the agent to infer usage solely from the name and description. No context is given about which scenarios call for this tool rather than another.

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