ncloud_ses_get_dashboard

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

The annotation readOnlyHint=true indicates a safe read operation, but the description adds no further behavioral details. It does not disclose what 'dashboard information' includes, nor does it mention output format or limitations. Without an output schema, the agent is left blind on what data to expect.

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 with no redundant information. It is front-loaded with the verb and resource, making it easy to parse.

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 absence of an output schema and the tool's specific function (dashboard for a complex service), the description is too sparse. It should outline what kind of information is returned (e.g., metrics, status, charts) to be considered complete.

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 covers the sole parameter with a brief description. The tool description echoes the resource context but does not add meaning beyond 'Cluster instance number'. With 100% schema coverage, the baseline is 3, but no extra semantic value is provided.

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 action ('Get dashboard information') and the resource ('Search Engine Service cluster'). It distinguishes this tool from other SES getters like ncloud_ses_get_cluster_detail as it specifically targets dashboard data.

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 explicit guidance on when to use this tool versus alternatives. While the read-only annotation hints at safe usage, the description does not provide context such as prerequisites (e.g., needing cluster instance number) or when not to use it.

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