ncloud_gtm_get_geo_cidr_map_detail

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

Annotations already declare readOnlyHint=true, so the agent knows this is a safe read operation. The description adds 'detailed information' but doesn't disclose additional behavioral traits (e.g., what fields are returned, if any side effects). It does not contradict annotations.

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, front-loaded sentence that directly states the purpose. Every word earns its place with no wasted 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?

Without an output schema, the description should provide more detail on what 'detailed information' includes (e.g., fields like geo locations, CIDR blocks). The current description is adequate but leaves the agent uncertain about the returned data structure.

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% for mapId with a clear description. The tool description adds context by specifying that the map is a 'Geo or CIDR map', which enhances understanding of the parameter's purpose beyond the schema alone.

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 action ('Get detailed information about a specific Geo or CIDR map') with a specific verb and resource. It distinguishes from sibling tools like 'ncloud_gtm_list_geo_cidr_maps' by emphasizing 'specific', indicating this is for retrieving details of one map rather than listing all.

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 (retrieve details of a specific map when ID is known) but does not explicitly state when to use this vs alternatives like listing maps or creating maps. No when-not or alternative tool references provided.

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