ncloud_put_bucket_cors

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

Annotations are empty, so the description must disclose behavioral traits. It indicates a write operation but does not mention side effects (e.g., overwriting existing rules), permissions required, idempotency, or error conditions. This is a significant gap for a mutation tool.

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 concise with two sentences, front-loading the main purpose and adding relevant detail. No unnecessary words.

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?

No output schema exists, but the description does not mention return values or error handling. For a PUT operation, the agent would benefit from knowing that success returns 200 OK and what errors might occur (e.g., invalid rules, bucket not found). The description is incomplete for full context.

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%, so baseline is 3. The description adds no additional meaning beyond the schema properties; it only summarizes the parameters without providing extra context or examples.

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 tool sets CORS configuration for a Ncloud Storage bucket, specifying it defines allowed origins, methods, and headers. The verb 'Set' and resource are specific, and it distinguishes from siblings like get_bucket_cors and delete_bucket_cors.

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 for configuring CORS but does not explicitly state when to use this tool versus alternatives (e.g., get_bucket_cors to read, delete_bucket_cors to remove). No guidance on prerequisites or when not to use it.

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