ncloud_validate_policy

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

Beyond the read-only/idempotent annotations, the description discloses that it makes an actual server-side API call and explains the return semantics: success plus INFO/WARNING/ERROR details, with ERROR indicating rejection. This materially helps an agent interpret results without an output 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?

Two tight sentences front-load the core action and server-side behavior, then add the return interpretation and the no-side-effect guarantee. Every clause earns its place with no redundancy.

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 safe validation tool, the description covers what it does, where it runs, how to interpret results, and the absence of side effects. The detailed nested permissions schema handles parameter specifics, so no critical guidance is missing.

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 the schema fully documents policyName, description, and permissions. The description adds no parameter-level detail, but none is needed because the schema already carries that burden.

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 uses a specific verb ('Validate') with a clear resource ('user-created policy definition on the SERVER before creating it'). It distinguishes itself from a dryRun preview and from policy creation/update siblings, so an agent knows exactly what this tool does.

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 phrase 'before creating it' gives a clear when-to-use condition, and 'No policy is created' clarifies the boundary with creation tools. It contrasts with a dryRun preview, though it does not explicitly name an alternative tool such as ncloud_create_policy, so a small gap remains.

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