ncloud_edge_get_profile

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

Annotations only declare readOnlyHint=true; the description contributes real behavioral context by revealing that no single-profile endpoint exists and the result is derived by filtering the list, which affects expected latency and completeness. It does not describe behavior when the ID is absent, so it falls short of a 5.

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 front-loaded sentence with the core action first and the mechanism as a brief parenthetical. No filler, no restatement of the tool name.

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 one-parameter read tool with annotations covering the safety profile, the description supplies everything needed to invoke it correctly, including the list-filtering caveat. It stops short of describing the returned profile shape, though with no output schema a brief note on the response would have made it fully self-contained.

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?

With one parameter and 100% schema description coverage, the schema already documents profileId. The description confirms the ID-based lookup but adds no format, range, or source-of-ID guidance, so the baseline 3 applies.

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 and resource ('Get a specific Global Edge profile') and pins the selector ('by ID'), which cleanly separates it from the sibling list_profiles tool. The parenthetical even explains the underlying mechanism, so the agent knows exactly what this returns relative to list_profiles.

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 makes clear this is the way to obtain one profile when you already hold an ID, and the note that it filters the profile list implicitly routes agents to ncloud_edge_list_profiles for bulk retrieval. It never explicitly says when NOT to use it (e.g., to enumerate profiles), so a 4 rather than a 5.

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