ncloud_serverless_list_logs

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

Annotations already declare readOnlyHint=true, covering the safety profile. The description adds context about the 'lastFile (currently written)' field, which is a useful behavioral trait, but does not disclose other aspects like pagination behavior or error handling. Since annotations carry the safety burden, a 3 is appropriate for the added context without contradiction.

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, well-structured sentence. It front-loads the action, then the endpoint, followed by returned fields and sort fields. No filler or redundancy; every clause contributes to understanding the tool's behavior.

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 description lists the fields returned and sort capabilities, which is sufficient for an agent to understand the response shape and options. Pagination is implied by the schema's pageNo and pageSize, so the description need not repeat it. Minor gaps like error responses or prerequisites are not critical for a read-only list operation.

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% with all parameters documented. The description adds value by enumerating the allowed sort fields (name, lastModifiedDateTime, fileSize), which the schema only specifies via pattern and not explicitly. This compensates for the schema's lack of field enumeration, making the sort parameter clearer.

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 action (list log files of an instance) with the endpoint and lists the returned fields (name, logType, fileSize, lastModifiedDateTime, lastFile). It distinguishes itself from sibling log tools like export or delete by focusing on enumeration. The verb and resource are specific and unambiguous.

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?

No guidance on when to use this tool versus alternatives such as ncloud_serverless_export_logs or ncloud_serverless_batch_delete_logs. It does not mention typical use cases, prerequisites, or conditions where another tool would be preferred. The agent must infer its purpose from the name and description alone.

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