ncloud_serverless_get_operation

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

Beyond the readOnlyHint annotation, the description discloses the response structure (done, metadata, results for clusters only, error, failures for batch) and gives explicit polling semantics. This helps the agent interpret the response and determine completion without opening an output schema.

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 two sentences with no filler. The core action is front-loaded, followed by the response fields and polling rule in a compact, structured format.

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 complex (16 endpoints) and has no output schema, but the description covers the essential behaviors: what fields to expect, the resourceType routing, and the polling success condition. Combined with the 100% schema coverage, an agent has enough to call and interpret the result.

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%, so the schema already documents all four parameters including when clusterName and instanceName are required. The description adds only marginal context about resourceType routing and result availability, which is helpful but not necessary for parameter understanding.

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 opens with a specific verb and resource ('Get an asynchronous operation') and explains that it aggregates 16 get*Operation endpoints routed by resourceType. This distinguishes it from sibling tools like ncloud_serverless_list_operations, which lists operations rather than fetching a single one.

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 implies usage: poll with an operationId until done=true, and states the success condition. It does not name alternative tools or explicitly state when not to use it, but the context is clear that this is the endpoint for checking a single operation's status.

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