ncloud_edge_get_edge_stats

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

The description states 'Get traffic statistics', which is consistent with the readOnlyHint annotation. No additional behavioral traits (e.g., pagination, data format, rate limits) are disclosed beyond what the annotation provides. The annotation already identifies it as read-only, so the description adds marginal value.

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, concise sentence that communicates the core purpose without any wasted words. It is front-loaded with the action and resource.

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?

Despite having no output schema, the description does not specify what traffic statistics are returned (e.g., bytes transferred, requests, status codes) or any constraints like maximum date range. The agent lacks crucial information to understand the output format, making the description incomplete for a tool with 4 required parameters and no output schema.

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%, with each parameter (profileId, edgeId, startDateTime, endDateTime) already described in the schema. The description adds no semantic information about parameters beyond what the schema provides.

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'), the resource ('traffic statistics for a Global Edge CDN edge'), and the scope ('within a specified time range'). It distinguishes this tool from sibling tools like ncloud_edge_list_edges (which lists edges) and ncloud_edge_get_edge_status (which gets status), by specifying statistics retrieval.

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 when traffic statistics are needed, but does not explicitly state prerequisites (e.g., needing profileId and edgeId from list tools) or when not to use this tool. Guidance is implicit via the name and description, not explicit.

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