ncloud_secret_get_secret_logs

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

readOnlyHint=true already tells the agent this is a safe read, so the bar is lower. The description does add one useful piece of content context — that the output includes rotation job tokens — but says nothing about ordering, retention window, or pagination behavior of the log results.

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 filler; the parenthetical adds content scope efficiently. Slightly terse given the tool's 7-parameter surface, but nothing is wasted.

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 read-only log fetch with a fully documented schema and annotations covering safety, the description is adequate but thin: it doesn't clarify the log entry shape or whether pagination must be driven manually, which is the main remaining ambiguity.

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 every parameter (pageNo, pageSize, keyword, timestamps, keyIsolation) is documented in the schema itself. The description adds no parameter-level meaning, so the baseline 3 is appropriate.

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 states a specific verb ('Get') and resource ('usage / rotation logs of a secret'), so an agent immediately knows what is returned. It does not, however, distinguish itself from the many neighboring ncloud_secret_* tools (get_secret, list_triggers, etc.), so sibling differentiation is left to the name alone.

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?

There is no statement of when to call this versus alternatives, nor any prerequisites (e.g., that the secret must exist or be rotation-enabled). Usage must be inferred from the name and the phrase 'usage / rotation logs'.

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