ncloud_advisor_download_item_results

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

Annotations already declare readOnlyHint=true, so the safe-read profile is covered. The description adds the dual output mode (file save vs inline base64), which is useful behavioral context, though it largely restates what the savePath schema description already says. No pagination, size-limit, or auth details beyond that.

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?

Two short sentences, with the core purpose front-loaded and the output behavior second. No filler or redundancy.

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?

No output schema exists, but the description explains the two return modes (savePath file or base64 inline). Combined with a 100%-covered schema and readOnly annotation, an agent has enough to call it correctly; only the item/category relationship to sibling tools is left implicit.

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 all three parameters (itemCode, savePath, categoryCode) are already documented in the schema. The description only echoes the savePath behavior and adds nothing about itemCode or the categoryCode enum, so baseline 3 is appropriate.

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 (Download) and resource (Excel report of check results) with an explicit scope qualifier ('for a specific check item'). That scope cleanly distinguishes it from the sibling item/category/all download variants without needing to name them.

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?

The phrase 'for a specific check item' implies when to use this over the category/all downloads, but there is no explicit when-to-use guidance, prerequisite (e.g., must item be refreshed first), or named alternative. Usage is inferred rather than stated.

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