ncloud_edge_get_edge

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

The annotation readOnlyHint=true is consistent with 'Get'. The description adds that it includes origin, caching, and access control settings, but does not disclose other behavioral aspects like required permissions, response structure, or whether it returns a snapshot of current config.

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 that concisely conveys the purpose and key details without any wasted words. It is front-loaded with the action and resource.

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 read tool with one parameter and no output schema, the description covers the main purpose and key config aspects. However, it could be more complete by noting that it returns the full configuration details or mentioning the absence of output schema.

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% for the single parameter 'edgeId' described as 'Edge ID to query'. The description does not add extra meaning beyond the schema, so it meets the baseline but no more.

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 it 'Get detailed configuration of a specific Global Edge CDN edge' with specific components (origin, caching, access control). It distinguishes from sibling tools like ncloud_edge_list_edges (list) and ncloud_edge_get_edge_status (status) by focusing on configuration details.

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 vs alternatives. While the purpose implies it's for retrieving detailed config of a single edge, it doesn't mention when to prefer ncloud_edge_get_edge_status or ncloud_edge_get_edge_stats, nor does it caution against misuse.

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