ncloud_edge_rename_profile

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

With no annotations, the description carries the full behavioral burden, yet it only restates the mutation. It does not disclose permission requirements, whether the old name is freed, what happens if the name collides (a check-profile-name sibling exists), or error behavior. The word 'existing' is the only added signal.

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 verb and resource up front and no filler. It is efficient, though correspondingly sparse on everything else.

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 simple two-parameter mutation with full schema coverage and no output schema, the description is minimally adequate. It omits uniqueness/validation behavior and any interaction with the sibling name-check tool, which an agent would need for correct invocation.

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%: both profileId and name (including the 3-35 char format restriction) are fully documented in the schema. The description adds no format or constraint detail beyond it, 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 (rename) and resource (Global Edge CDN profile), clearly distinguishing it from sibling read tools like ncloud_edge_get_profile and ncloud_edge_list_profiles. It does not explicitly name a sibling, but the verb+resource pair is unambiguous.

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?

No guidance on when to use this versus ncloud_edge_create_profile, ncloud_edge_get_profile, or ncloud_edge_check_profile_name. An agent must infer that renaming implies the profile already exists, but nothing tells it how to resolve the profile or whether to pre-check the name.

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