decode_b2m

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

No annotations provided, so description must disclose behavior. It says 'Heuristically classify' and 'Offline', but fails to explain what the heuristic entails, whether it is read-only, or any side effects. No mention of error conditions or assumptions.

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?

Description is a single sentence, concise but too brief. It front-loads purpose but lacks any structuring or additional details. Could be expanded moderately without losing conciseness.

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 a complex nested object parameter, no output schema, and no annotations, the description is severely insufficient. Agent has no guidance on input format, output expectations, or heuristic behavior.

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 single parameter 'tx' is a black-box object with no schema details. The description does not clarify what 'tx' should contain (e.g., transaction object, hex blob, JSON). With 0% schema description coverage, the parameter is entirely undocumented.

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 states the tool classifies a Burn2Mint-related transaction, specifying the verb 'classify' and resource 'Burn2Mint transaction'. It adds bridge direction context (XRPL↔Xahau) and offline nature. However, 'Heuristically' introduces ambiguity, and it doesn't distinguish from other decode tools like decode_tx_blob.

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?

No guidance on when to use this tool vs alternatives. The only hint is 'Offline', implying no network calls, but no explicit when-to-use or when-not-to-use. Sibling tools include many decode functions, but no comparative advice.

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