ncloud_edge_get_purge_request

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

The readOnlyHint=true annotation already declares this a safe read, so the burden is lighter. The description confirms it retrieves 'status/details' but adds nothing about polling cadence, eventual-consistency, retention, or what states a purge request can be in, which would be genuinely useful here.

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 front-loaded sentence with no waste. It is appropriately sized, though it is arguably a touch too terse for a tool whose only purpose is status inspection.

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 one-parameter read tool with no output schema, the description is minimally adequate. It signals that status and details are returned, but does not describe the shape of the response, which matters more given there is no output schema to fall back on.

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 description coverage is 100% and the single parameter is already documented as the 'Purge request ID returned by ncloud_edge_purge'. The description adds no further parameter semantics, so the baseline 3 applies.

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 gives a clear verb+resource ('Get the status/details of a Global Edge purge request'), distinguishing this read operation from the write sibling ncloud_edge_purge. It is easy to tell what the tool does, but it never explicitly names the companion purge tool or clarifies the relationship between them.

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?

Usage is only implied: an agent can infer this is for polling the outcome of a purge, and the schema's param note links the ID back to ncloud_edge_purge. However, the description itself offers no explicit when-to-use, when-not, or alternative guidance.

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