ncloud_edge_edit_edge

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

Annotations are empty, so the description carries full responsibility for disclosing behavior. It only says 'Edit', implying mutation, but does not specify side effects, idempotency, synchronization, success response, or potential downtime. For a mutation tool with no annotations, this is insufficient.

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 two sentences with no unnecessary words. It is front-loaded with the primary purpose and succinctly states the key requirement. Every sentence earns its place.

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 mention what the tool returns (e.g., updated configuration or success status). It also does not address post-conditions like whether the edge is restarted. For a tool with 2 required params and no output schema, the description is incomplete.

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 both parameters described. The description repeats 'provide the full edge configuration as a JSON object,' which adds minimal value beyond the schema. It does not explain the structure of the JSON or how to obtain it (though hinted in param description). Baseline 3 is appropriate.

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 (edit), the resource (existing Global Edge CDN edge configuration), and the input format (full edge configuration as a JSON object). It distinguishes itself from sibling tools like ncloud_edge_create_edge or ncloud_edge_get_edge by specifying 'edit an existing'.

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 the workflow by mentioning 'get current config from ncloud_edge_get_edge' in the parameter description, but the main description does not explicitly state when to use this tool vs alternatives or provide prerequisites. It does not mention that the full configuration must be provided, which could lead to confusion if the agent expects partial updates.

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