agentek-eth

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

No annotations are provided, so the description carries full burden of behavioral disclosure. While 'Reverse a pending transfer' implies a write/mutation operation, the description doesn't disclose critical behavioral aspects: whether this requires specific permissions, what happens to the reversed transfer, whether the action is reversible, potential side effects, or error conditions. For a mutation tool with zero annotation coverage, this is a significant gap.

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, efficient sentence with zero wasted words. It's appropriately sized for a tool with only two parameters and gets straight to the point without unnecessary elaboration.

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 mutation tool ('Reverse') with no annotations and no output schema, the description is inadequate. It doesn't explain what happens after reversal, what the tool returns, error conditions, or how this differs from related SLOW contract tools. Given the complexity implied by 'SLOW contract' operations and the lack of structured behavioral information, the description should provide more complete context.

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 coverage is 100%, with both parameters (chainId, transferId) clearly documented in the schema. The description doesn't add any parameter-specific information beyond what's already in the schema descriptions. With complete schema coverage, the baseline score of 3 is appropriate since the schema does the heavy lifting for parameter documentation.

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 ('Reverse') and target resource ('a pending transfer in SLOW contract'), providing specific verb+resource pairing. However, it doesn't differentiate from sibling tools like 'canUnlockSlow', 'intentUnlockSlow', or 'getCanReverseSlowTransfer', which appear related to similar SLOW contract operations.

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 provides no guidance on when to use this tool versus alternatives. With many sibling tools related to SLOW contracts (canUnlockSlow, intentUnlockSlow, getCanReverseSlowTransfer, intentApproveSlowTransfer, etc.), there's no indication of prerequisites, constraints, or appropriate contexts for choosing this specific reversal tool.

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