ncloud_cdnplus_get_purge_history

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

Annotations declare readOnlyHint=true, so the safe-read nature is known. However, the description adds no behavioral context beyond that—nothing about response format, pagination, default behavior when no purge IDs are given, or ordering. It essentially restates the schema, so minimal value added.

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, front-loaded with the action ('Get') and object, and includes the optional filter concisely. No wasted words.

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-only operation with two parameters and clear schema, the description is mostly complete. It states the main purpose and optional filtering, which is sufficient for an agent to invoke the tool. The lack of pagination or return-format details is a minor gap, but acceptable for a straightforward list/history endpoint.

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%, with both parameters ('purgeIdList' and 'cdnInstanceNo') described in the schema. The description's phrase 'optionally filtered by purge IDs' adds no new meaning beyond the schema. Baseline 3 is appropriate since the schema handles the semantics.

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 verb 'Get', the resource 'CDN+ purge request history', and the scope 'for an instance', with an optional filter by purge IDs. It distinguishes from sibling tools like ncloud_globalcdn_get_purge_history and ncloud_cdnplus_request_purge by specifying 'CDN+' and 'purge request history'.

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 when you need purge history for a specific CDN+ instance, but it does not explicitly state when to use this tool versus alternatives, nor does it mention exclusions or prerequisites. The context is clear enough for an agent to infer, but explicit guidance is missing.

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