ncloud_ses_get_dashboard

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

The description adds no behavioral context beyond what the readOnlyHint annotation already conveys. It does not describe the return format, pagination, rate limits, or any side effects. Since the annotation already indicates safety, the description is expected to add extra context but fails to do so.

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 that directly states the tool's purpose. Every word adds value, with no redundancy or filler, making it optimally concise.

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 tool is simple (one parameter, read-only) and the schema covers the parameter, so the description is minimally adequate. However, without an output schema or any hint of what 'dashboard information' includes, the description lacks enough context to fully prepare an agent for the response. A bit more specificity would improve completeness.

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 schema fully documents the single parameter (serviceGroupInstanceNo) with the description 'Cluster instance number'. The tool description adds no additional semantic meaning, but with 100% schema coverage the baseline of 3 is appropriate.

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 verb 'Get' and the resource 'dashboard information for a Search Engine Service cluster', identifying the tool's purpose without being tautological. However, it does not explicitly differentiate this from sibling tools like ncloud_ses_get_monitoring or ncloud_ses_get_cluster_detail, so it earns a 4 rather than a 5.

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 provides no guidance on when to use this tool versus alternatives such as ncloud_ses_get_cluster_detail or ncloud_ses_get_monitoring. There is no mention of prerequisites, exclusions, or typical use cases, leaving the agent to infer usage solely from the tool name.

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