ncloud_datafence_list_file_exports

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

readOnlyHint=true already tells the agent this is a safe read, and the description adds nothing beyond that: no pagination behavior, no ordering, no statement of what is returned or whether results are filtered by default. For a 7-parameter list tool the description carries no behavioral weight of its own.

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 no filler and the resource front-loaded. It is efficient, though arguably under-specified rather than deliberately minimal.

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?

The schema fully documents all 7 parameters and the annotation covers the safety profile, so the basics are covered. Still, a list operation with no output schema and no description of pagination or filter semantics leaves the agent guessing about result shape and how to page through large export histories.

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 coverage is 100%, so every parameter including from/to date format, page/size defaults, status filter, and the fenceId/boxId cross-references to sibling lookup tools is already documented in the schema. The description's phrase "of a Box" only loosely reinforces that boxId scopes the query, so the 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 clear verb+resource ("List file export requests") scoped to a Box, so the operation is unambiguous. However, it does not differentiate itself from closely named siblings such as ncloud_datafence_get_file_export, ncloud_datafence_create_file_export, or ncloud_datafence_list_export_approvals.

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 when-to-use guidance, no mention that this is the collection-level counterpart to get_file_export, and no hint about using the status/from/to filters to narrow results. 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.