ncloud_functions_list_packages

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

The annotations already declare readOnlyHint=true, indicating the tool is safe for read-only access. The description adds no additional behavioral details such as pagination behavior, rate limits, or whether the listing is affected by the platform parameter. Since the description carries the burden when annotations are minimal, this is insufficient.

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, concise sentence that directly states the purpose. It is appropriately front-loaded with no wasted words. However, it could be slightly expanded with context without losing conciseness.

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 tool with one optional parameter and no output schema, the description is minimally adequate. It does not explain what a package is or how this tool relates to other functions tools (e.g., list_actions, list_triggers). Given the complexity of the sibling tools, more context would help an agent differentiate.

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 input schema has 100% description coverage for the single optional parameter 'platform'. The description does not add any meaning beyond what the schema already provides, which is the verbatim 'Platform type (default: vpc)'. Baseline score of 3 is appropriate as per rules.

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 'List all Cloud Functions packages' clearly states the verb (List) and the resource (Cloud Functions packages), distinguishing it from sibling tools like get_package, create_package, and delete_package. However, it does not specify the scope (e.g., region or account), which would enhance clarity.

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 is provided on when to use this tool versus alternatives. For example, it does not mention that to get details of a specific package, one should use ncloud_functions_get_package. The description lacks context about prerequisites or typical use cases.

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