ncloud_get_custom_resource

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

The readOnlyHint annotation already indicates this is a safe read operation, and the description does not contradict this. Yet it adds no additional behavioral context (e.g., error behavior, return format, permission requirements) beyond what the annotation and name already imply.

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?

A single, direct sentence with no filler. The purpose is front-loaded ('Get detailed information') and the resource and scope are immediately clear. Every word earns its place.

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?

For a simple one-parameter getter with a read-only annotation, the description is adequate. It indicates the action, the resource type, and the scope. It does not specify return fields or error cases, but the lack of an output schema makes that less critical. Still, it could be slightly more descriptive about what 'detailed information' entails.

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 only parameter (resourceId) with a clear description ('Custom resource ID'), and schema coverage is 100%. The description adds no new parameter details, so it meets the baseline without further contribution.

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 uses a specific verb ('Get') and resource ('detailed information about a specific custom resource in Cloud Insight'), clearly distinguishing it from list, create, update, and delete operations. The scope ('in Cloud Insight') adds context that separates it from other resource types.

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 clearly implies the tool is for fetching a single resource when you have a specific resource ID, as opposed to listing resources. However, it does not explicitly state when not to use it or mention alternatives like list_custom_resources, so it lacks explicit exclusions but provides clear context.

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