hermes_approveSubmit a previously approved request for execution by providing its approval ID. The request is consumed once and executed unchanged, which may trigger external side effects.
Consume a prepared approval ID exactly once and submit the unchanged request for execution. This can cause external side effects.
| Name | Required | Description | Default |
|---|---|---|---|
| approvalId | Yes |
Changes observed during successful MCP inspections.
v0.6.1Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already provide destructiveHint=true. Description adds value by noting 'consume exactly once' and 'can cause external side effects', reinforcing and extending annotation context.
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 first sentence; side effect warning is second. Perfectly sized for a simple tool.
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?
Given one parameter, no output schema, and existing annotations, description covers essential behavior and side effects. Lacks details on post-execution status but sibling tools fill that gap.
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 0% so description must compensate. It adds context 'prepared approval ID' but does not fully explain the parameter's origin or validation beyond what the schema provides.
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?
Description uses specific verbs 'consume' and 'submit' with resource 'prepared approval ID', clearly distinguishing it from sibling tools like hermes_prepare and hermes_reject. It states the action is exactly once and unchanged.
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?
Clearly implies use after hermes_prepare, but does not explicitly exclude other contexts or mention alternatives. Contrasts implicitly with hermes_reject and hermes_cancel.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.