ncloud_gtm_list_profiles

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

The readOnlyHint annotation already establishes that this is a safe read operation, lowering the bar. The description adds a useful clarification that profiles are domains and mentions pagination/filtering, but it does not disclose return format, ordering, or potential edge cases beyond what the schema and annotation already convey. No contradiction with 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 sentence that front-loads the operation and resource. It is concise, clear, and contains no redundant or filler wording.

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 list operation with three optional parameters and no output schema, the description adequately captures the resource type and available filters. It could be slightly more complete by explicitly pointing to the detail tool for full profile information, but it is sufficient for a straightforward listing use case.

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 the schema fully documents the three parameters. The description merely restates the name filter and pagination without adding new meaning, constraints, or examples beyond what is already in the schema.

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 uses a specific verb ('List') and a specific resource ('Global Traffic Manager profiles (domains)'), and it clarifies scope with optional pagination and name filter. This clearly distinguishes it from sibling tools like ncloud_gtm_list_policies and ncloud_gtm_get_profile_detail.

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 verb 'List' implies the primary use case of enumerating profiles, and sibling detail/create/update tools are natural alternatives by naming convention, but the description gives no explicit guidance on when to choose this tool over those alternatives or when to apply the optional filters. It provides context but no exclusions.

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