inspect_emitted_tx

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

Discloses outputs: tx JSON, plain-English summary, danger score. Mentions non-destructive offline nature. With no annotations, description fully carries burden and provides clear behavioral insight.

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. Front-loaded with core action and output, then context. Every sentence earns its place.

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 no output schema, description covers return values sufficiently. Single parameter is well-documented. Tool is simple and description is complete for its purpose.

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 a clear description of 'emitted'. Description reinforces it but does not add significant new meaning beyond schema, so baseline 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?

Description specifies verb 'decode' and resource 'emitted blob hex(es) from an execute_hook result'. It clearly distinguishes from sibling decode tools by focusing on hook emit output, not general transaction blobs.

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?

States it is used after execute_hook ('Closes the loop on emitter hooks') and is 'Offline', giving clear context. However, it does not explicitly mention when not to use or list alternatives.

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