ncloud_edge_list_certificates

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

Annotations already indicate readOnlyHint=true, so the tool is clearly read-only. The description adds that it lists 'all provisioned' certificates, but does not disclose pagination behavior, performance, or whether it returns only active certificates. This adds some context but is limited.

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 with no extraneous information. It is efficient, though it could be slightly more informative without becoming verbose.

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?

The tool is a list operation with pagination, and no output schema is provided. The description covers the main purpose but lacks details on output format, defaults, or behavior when no certificates exist. It is adequate but not fully complete.

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 both parameters (pageNo, pageSize) fully described in the input schema. The tool description adds no additional meaning beyond that, so it meets the baseline for high coverage.

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 it lists all provisioned SSL/TLS certificates for Global Edge CDN, using a specific verb ('List') and resource ('certificates'). It implicitly distinguishes from sibling tools like ncloud_edge_get_certificate (single certificate) and ncloud_list_certificates (likely for a different service).

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 listing certificates for Global Edge CDN but provides no explicit guidance on when to use this tool versus alternatives or when not to use it. Sibling tools like ncloud_edge_provision_certificate or ncloud_edge_delete_certificate exist, but no differentiation is given.

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