Transform AIS Encrypted Payload

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

Annotations provide readOnlyHint=true, suggesting no side effects. The description mentions session-key mode but adds little beyond what's in the schema (keySource enum). No disclosure of error behavior or other traits.

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 sentences with clear front-loading of the primary action and algorithms. No redundant information, but could be slightly improved by ordering key details first.

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?

With 5 parameters, 3 enums, and no output schema, the description is too brief. It lacks explanation of return values, parameter relationships, error handling, and behavior when keySource is not session.

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 0%, and the description does not explain individual parameters like key, value, algorithm, keySource, or operation. For example, it omits that key is only needed when keySource=custom, or that value can be complex types.

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 (encrypt/decrypt) and resource (AIS payload) with supported algorithms (AES, DES, TripleDES, Rabbit). It is distinct from sibling tools which are primarily auth and student operations.

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 through session-key mode derivation, but does not explicitly state when to use encrypt vs decrypt, when to choose algorithms, or prerequisites like an active session. No alternatives are mentioned.

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