ncloud_functions_get_package

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

Annotations already declare readOnlyHint=true, so the safety profile is established. The description adds useful context about what the response contains, which helps an agent judge whether the tool satisfies the request. No contradictions with the annotation.

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 efficient sentence that front-loads the verb and resource, then lists deliverables in a compact colon-delimited form. No wasted words, though slightly denser formatting with a list would improve scannability.

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 two-parameter read tool with full schema coverage and a readOnlyHint annotation, the description is nearly complete. It states what the operation returns, and nothing an agent needs to invoke it successfully is missing.

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%, so both platform and packageName are already fully documented. The description adds no new parameter-level detail; it only echoes the concept of 'platform' as a returned attribute, which is not parameter guidance.

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'), resource ('a Cloud Functions package'), and enumerates the returned contents (description, default parameters, platform, actions). This distinguishes it from the sibling get_action (single action) and list_packages (enumeration), though without naming them explicitly.

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?

Usage context is implied: the tool fetches a single package's full detail, contrasting with list_packages for enumeration. However, the description never states when to prefer this tool over ncloud_functions_list_packages or ncloud_functions_get_action, leaving the routing decision to inference.

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