ncloud_kms_encrypt

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

Contradicts annotations: description says 'Encrypt data' (write operation) but annotations set readOnlyHint=true. Beyond that, it discloses size limit and key types but omits other behavioral traits like output format, error handling, or dependencies.

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 short sentences, front-loaded with the core action and constraints. 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?

Missing critical information: no description of return value (ciphertext), no error scenarios, no prerequisites like key availability. For a non-trivial tool like encryption, this 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% (all parameters documented in schema). Description does not add significant additional meaning beyond what the schema already provides. 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?

Clearly states the tool encrypts data up to 32KB using the current version of a KMS key, and specifies supported key types (AES256, RSA2048). This distinguishes it from sibling tools like decrypt, sign, verify.

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?

Implied usage through the description, but no explicit guidance on when to use this tool versus alternatives (e.g., sign/verify, or other encryption methods). No exclusions or prerequisites mentioned.

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