ncloud_edge_get_edge_stats

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

Annotations already establish readOnlyHint=true, so the safety profile is covered. The description adds a genuine behavioral constraint beyond the annotations: the time range must be UTC and cannot exceed 730 days back. That retention window is a real operational limit an agent needs and cannot infer from the schema.

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?

A single well-formed sentence with zero waste, and the resource and scope are front-loaded before the parenthetical constraint. Appropriately sized for the tool's simplicity.

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 read-only stats tool with complete parameter documentation and a readOnly annotation, the description covers the essentials. However, with no output schema it never hints at what the statistics summary contains, leaving the agent without any expectation of the return payload.

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 dateFrom/dateTo/edgeId/profileId all documented inline, so the baseline is 3. The description adds only the 730-day/UTC constraint on the date range, which is meaningful but not parameter-syntax detail beyond what the schema supplies.

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?

States a specific verb (Get), resource (traffic statistics summary), and scope (Global Edge CDN edge within a time range). This clearly distinguishes it from the sibling ncloud_edge_get_edge_status, which retrieves operational status rather than traffic metrics, though it does not name that sibling explicitly.

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 when the tool is used (retrieving traffic stats for an edge over a time range) but gives no explicit when-to-use vs. when-not-to-use guidance and names no alternative sibling. Nothing routes the agent between this and adjacent edge tools.

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