ncloud_databox_list_export_requests

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

readOnlyHint=true already tells the agent this is a safe read, so the description's only remaining job is to add context such as pagination behavior, result ordering, or filtering semantics — and it adds none. It effectively restates the tool name with no behavioral disclosure beyond it.

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 zero filler. Nothing in it is wasted.

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 endpoint with a fully documented schema and no output schema, the definition is serviceable but thin: it omits pagination expectations, what an export request record contains, and how the date-range filters behave. Enough to call correctly, not enough to call confidently.

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%, with pageNo, pageSize, dataBoxNo, applyStartDate, and applyEndDate all documented inline, so the baseline is 3. The description contributes nothing extra, such as how date filters interact or what the page defaults are.

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) plus a concrete resource (file export requests) scoped to a Data Box, so the agent knows it is a read/list operation. It does not, however, distinguish itself from nearby siblings such as ncloud_databox_get_export_request (single request) or ncloud_databox_list_import_requests (the import counterpart).

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 guidance on when to use this list tool versus ncloud_databox_get_export_request for a single request, nor any mention of prerequisites or exclusions. The agent must infer usage entirely from the name.

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