ncloud_gtm_list_policies

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

Annotations already declare readOnlyHint=true, so the description's 'List' is consistent. The description adds that pagination and filters are optional, which is slight extra context, but this mostly restates what the schema already documents. No additional behavioral traits (e.g., default page size, return format, rate limits) are disclosed.

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 with no wasted words. It conveys the action, resource, and key capability (pagination/filters) efficiently.

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?

This is a simple read-only list tool with 5 optional, fully documented parameters and a readOnlyHint annotation. While there is no output schema, the description's 'List policies' adequately implies a list of policy objects is returned. It could mention default pagination values or return shape, but for a straightforward list operation, the coverage 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 description coverage is 100% - each of the 5 parameters has a clear description. The tool description only summarizes them as 'optional pagination and filters', adding no new meaning beyond what the schema provides. 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?

The description uses a specific verb 'List' with a clear resource 'Global Traffic Manager policies' and scoping qualifiers 'with optional pagination and filters'. This distinguishes it from sibling tools like ncloud_gtm_get_policy_detail (single policy) and ncloud_gtm_list_profiles (different resource).

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 intended use as a listing operation is implied by the verb 'List', but there is no explicit guidance on when to use this tool versus alternatives such as ncloud_gtm_get_policy_detail or ncloud_gtm_list_profiles. No exclusions or comparison to other tools are provided.

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