ncloud_datafence_list_export_source_nas

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

Annotations already declare readOnlyHint=true, so the safety profile is covered. The description adds only the export-source scoping concept and discloses nothing about permissions, result size, pagination, or how fenceId/boxId constrain the listing, so it contributes little behavioral context beyond 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 tight sentence with the resource and scope front-loaded and no wasted words. It is arguably under-explained, but as conciseness it is strong.

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 list tool with both parameters fully schema-documented and no output schema, the description is minimally sufficient. It nonetheless leaves the fence/box relationship to the result and the position of this call in the export workflow unstated.

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 the schema already points to ncloud_datafence_list_boxes and ncloud_datafence_get_datafence for the two IDs. The description adds no meaning to either parameter, so baseline 3 applies.

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?

States a specific verb (List) and resource (Box NAS volumes available as export sources), which is more precise than a bare 'list NAS volumes'. However, it does not explicitly distinguish itself from near siblings like ncloud_datafence_list_import_target_nas or ncloud_list_nas_volumes, leaving the agent to infer the export-vs-import distinction.

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 explicit when-to-use guidance or named alternative. The phrase 'files can be exported from' implies this is used before creating a file export, but the agent must infer that from the export-adjacent sibling names rather than the description.

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