ncloud_functions_list_packages

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

The readOnlyHint annotation already signals that this is a safe read operation, and the description does not contradict that. It adds minimal behavioral context beyond the annotation, such as the API version, but does not disclose pagination, result structure, or other runtime behavior. The annotation covers the core safety profile, so this is adequate but not rich.

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, front-loaded sentence that states the operation and resource without filler or repetition. Every word earns its place.

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 list operation with one optional, fully documented parameter and a read-only annotation, the description plus schema is nearly sufficient. It does not describe the return payload, but no output schema exists and the list semantics are strongly implied by the description.

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?

The schema covers 100% of the parameter semantics by defining the 'platform' enum, default value, and the region constraint for Singapore/Japan. The description itself adds no parameter-level detail, so it does not need to compensate. This matches the baseline for full schema coverage.

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 ('List') and the resource ('Cloud Functions packages'), and includes the API version for precision. It does not explicitly contrast with sibling tools like ncloud_functions_get_package or ncloud_functions_create_package, so it stops short of full sibling differentiation.

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 provides no guidance on when to use this tool versus alternatives such as ncloud_functions_get_package for a single package or ncloud_functions_list_actions for actions. There is no mention of exclusions, prerequisites, or preferred contexts, leaving the agent to infer usage solely from the name.

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