ncloud_datafence_get_box_custom_images

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

readOnlyHint=true already declares this as a safe read with no side effects, so the bar is lower. The description adds only that the images are 'custom' and filtered by Box server type; it says nothing about pagination, result volume, or what happens for an unsupported productCode.

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 well-formed sentence with the resource front-loaded and no filler. It is arguably a touch too terse given the sibling ambiguity, but nothing 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 simple read-only list tool with a fully described two-parameter schema and annotations covering safety, the description is adequate. However, given how many datafence-related listing tools exist, the lack of disambiguation from the fence-level variant leaves a real gap.

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 parameters are already fully documented, including the productCode enum and the pointer to ncloud_datafence_get_datafence for fenceId. The description's 'Box server type' mirrors the schema wording but adds no syntax or constraint detail.

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?

Specific verb (List) plus resource (custom server images) and scope (usable for a Box server type), so the agent knows what it returns. The only gap is that it does not distinguish itself from the near-identical sibling ncloud_datafence_get_fence_custom_images.

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 when-to-use statement, no prerequisites, and no mention of the fence-level counterpart ncloud_datafence_get_fence_custom_images that an agent could easily confuse with this one. Usage must be inferred entirely from the name and description.

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