deny_action

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

With no annotations, the description carries the full burden of behavioral disclosure. It indicates the tool mutates state (denying a request) and returns a receipt, but it does not disclose side effects, required permissions, irreversibility, or error conditions. The description is insufficient for an agent to fully understand the tool's behavior.

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?

The description is a single sentence that front-loads the main action and return values. It is concise and contains no filler, though it could be slightly more structured by separating action from return value details. It efficiently communicates the core purpose.

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 the tool has an output schema and relatively simple semantics, the description is moderately complete. It covers the action and return values, but it does not explain how this tool fits into a workflow with siblings like 'approve_action' or 'controlled_action', nor does it clarify what 'pending' implies about the request's state.

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?

The input schema has 100% description coverage, so the schema already documents both parameters. The description adds no additional meaning beyond what the schema provides. According to the guidelines, with high schema coverage, a baseline of 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?

The description clearly states the action ('Deny') and the resource ('pending human approval request'), and specifies the return value ('signed receipt JCS plus sha256'). This distinguishes it from its sibling 'approve_action' and provides a clear, specific purpose.

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 the tool is for denying a pending request, which provides basic context. However, it lacks explicit guidance on when to use it versus alternatives, prerequisites, or conditions like whether the request must be in a specific state. The phrase 'pending' hints at the context but is not detailed enough.

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