ncloud_cm2_list_recent_changes

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

Goes well beyond readOnlyHint by disclosing the auth constraint (main-account key only, 403 for Sub Account keys) and specific failure codes (2101 for no window). This is exactly the operational context an agent needs before calling.

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?

Front-loads purpose, then constraints in a compact sequence with no filler sentences. The provenance aside ('verified 2026-10-02 with NCP_ADMINISTRATOR') is the only slightly expendable detail.

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?

With no output schema, the description still covers inputs, auth, zone scope, and error behavior well. It stops short of indicating what the returned certificate entries contain, a minor gap for a list tool.

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%, so baseline is 3, but the description adds the mutual-exclusion rule the schema cannot express: exactly one of minutes, seconds, or startDateTime+endDateTime, with concrete consequences (2101, 0 rows) for violating it.

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?

States a precise verb+resource ('List certificates whose status changed recently') and scopes it to Certificate Manager 2.0, distinguishing it from ncloud_cm2_list_certificates, which enumerates certificates rather than recent status changes.

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?

Gives clear conditions: 'Public zone only' and 'Requires a main-account API key', so the agent knows when this call will work. It does not name a sibling alternative for the cases it excludes (e.g. when a Sub Account key is in play), leaving routing slightly implicit.

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