ncloud_apigw_get_product

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

Annotations already declare 'readOnlyHint: true', indicating a safe read operation. The description adds no additional behavioral context beyond the surface-level 'get detailed information'. It does not mention any potential side effects, authentication needs, or data freshness, nor does it contradict the 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, and there is no wasted text or redundancy.

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 has a single parameter and no output schema. The description is minimal and does not hint at what kind of 'detailed information' is returned (e.g., pricing, specs, region). While sufficient for a basic get operation, it could be more informative given the complexity of API Gateway products.

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 the parameter 'productId' described as 'Product ID to query'. The description does not add any additional meaning, format, or constraints beyond the schema. Baseline of 3 applies because the schema already covers the parameter.

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') and the resource ('a specific API Gateway product'). The verb 'Get' and noun 'product' are specific, and the sibling tool 'ncloud_apigw_list_products' contrasts with this single-item retrieval, providing clear differentiation.

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?

There is no explicit guidance on when to use this tool versus alternatives like 'ncloud_apigw_list_products'. The usage is implied by the name and description (use when you have a productId), but no exclusions or conditions are stated.

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