ncloud_get_public_ip_detail

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

Annotations already declare readOnlyHint=true, so the description's mention of 'Get' aligns but adds no additional behavioral context (e.g., rate limits, authentication needs, or what 'detailed information' includes). The description does not enrich beyond what annotations provide.

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 a single clear sentence that is appropriately front-loaded and contains no wasted words. Every word serves a purpose.

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 tool with one parameter and no output schema, the description is mostly complete. It clearly states what the tool does, though it does not elaborate on what 'detailed information' includes. Given the tool's simplicity, this is adequate.

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% with one parameter 'publicIpInstanceNo' described as 'Public IP instance number'. The description does not add any further meaning or constraints beyond the schema, so baseline score of 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?

The description 'Get detailed information about a specific public IP instance' uses a specific verb ('get') and resource ('public IP instance'), clearly distinguishing it from sibling tools like 'ncloud_list_public_ips' (list all) and 'ncloud_get_public_ip_target_servers' (target servers).

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 for retrieving details of a single instance but does not explicitly state when to use this versus alternatives like 'ncloud_list_public_ips' or 'ncloud_get_public_ip_target_servers'. No when-not or alternative guidance is provided.

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