ncloud_advisor_get_item_result_detail

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

Annotations already declare readOnlyHint=true. The description adds value by revealing that results are paginated and include instance status (GREEN/YELLOW/RED). This goes beyond the annotation to clarify the output format.

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?

The description is two short sentences, immediately stating the purpose and key behavioral details (pagination, status). No unnecessary words; front-loaded with critical information.

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, paginated tool with fully described parameters, the description covers the main aspects: purpose, pagination, and status output. Missing details like default page/size or display filter options are already in the schema, so the description is sufficient.

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 baseline is 3. The description does not add additional meaning beyond the schema; it only generally references 'specific check item', which is already covered by the itemCode and categoryCode parameter descriptions.

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?

The description clearly states the tool retrieves detailed per-instance check results for a specific check item, using clear verb ('Get') and resource. It differentiates from sibling tools like ncloud_advisor_get_item_result_summary by specifying 'per-instance' detail level.

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 description implies usage context (requires a check item and category) but does not explicitly guide when to use this tool over alternatives like ncloud_advisor_get_item_result_summary or ncloud_advisor_get_item_status. No when-not or exclusion criteria are provided.

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