Reveal a sealed result

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

Annotations already set readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds meaningful context that this operation reveals the plaintext value and that the handle comes specifically from fhe_encrypt/fhe_compute/fhe_private_eval, which helps the agent anticipate the tool's behavior beyond the structured fields.

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, no filler, and the core action is front-loaded. The usage condition is stated in the second sentence without unnecessary elaboration.

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 one-parameter reveal tool, the description fully explains what it does, where the handle comes from, and when to invoke it. There is no output schema, but the purpose of revealing plaintext implies the return value sufficiently. Nothing needed to call it correctly 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 coverage is 100% with the handle parameter described as 'Handle such as ct_1'. The description enriches this by specifying the handle originates from fhe_encrypt, fhe_compute, or fhe_private_eval, giving the agent a stronger mental model of what value to pass.

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 decrypts a handle produced by fhe_encrypt, fhe_compute, or fhe_private_eval, and that doing so reveals the plaintext result. The verb 'decrypt' plus the resource 'handle' and the source tools make the purpose unmistakable and distinct from siblings.

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?

It explicitly says to call this only when the user asked to see the plaintext result, providing a clear condition that separates this tool from the other FHE operations. No alternative is named, but the when-to-use guidance is explicit and sufficient for a tool with this simple role.

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