Prepare an external action for approval

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

Description clearly states the tool is non-executing, creates a short-lived approval ID, and must be followed by human approval. Annotations only have openWorldHint, so the description carries full burden and does so well.

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 wasted words. Core action is front-loaded: 'Create a local, non-executing preview and short-lived one-shot approval ID'.

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?

Despite good purpose and transparency, the description omits parameter semantics and return value information. With 7 params and no output schema, the agent lacks sufficient context to construct valid invocations.

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 has 7 parameters with 0% description coverage. The tool description does not explain any parameter (model, prompt, etc.), leaving the agent without guidance on how to fill them meaningfully.

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 creates a local preview and approval ID without invoking Hermes, and requires showing preview to human. It distinguishes from siblings (approve, reject, status, result) by focusing on preparation.

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 specifies when to use (before approval, without invoking Hermes) and implies the human-in-the-loop step. However, it lacks explicit when-not-to-use or alternatives beyond the sibling context.

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