transaction_deny

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

Annotations only include idempotentHint, so the description carries the burden of behavioral disclosure. It adds the key fact that the operation is not executed and is removed, which is helpful. But it omits whether the removal is reversible or what happens if the ID does not exist, leaving some ambiguity.

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 concise sentence that delivers all essential information with no filler. Every word adds value.

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 tool with one parameter and no output schema, the description effectively covers the core action and the key nuance of non-execution. It could elaborate on post-denial effects, but the simplicity of the tool makes the description largely sufficient.

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 covers the id parameter fully (100%), so the baseline is 3. The description's mention of 'by ID' aligns with the schema but adds no extra semantic detail beyond what the schema already states.

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 uses a concrete verb 'Deny and remove' and clearly identifies the resource as 'pending operation by ID'. This unambiguously distinguishes it from transaction_confirm, which approves instead of denies, and transaction_simulate, which tests without permanent action.

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 phrase 'without executing it' immediately conveys that this tool is for cancellation rather than execution, providing clear context. However, it does not explicitly name alternatives or state when not to use it, but the contrast with transaction_confirm is implicit.

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