Decode Safe calldata

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

Annotations already establish readOnlyHint=true, so safety is covered. The description adds useful behavior beyond that: it discloses that signature types are interpreted and that MultiSend batches are recursively decoded per inner call. It says nothing about handling of malformed/unsupported calldata or how failures are reported.

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?

A single dense sentence with no filler, and the most important scope information (Safe execTransaction, MultiSend) is front-loaded. It is appropriately sized for the tool's simplicity.

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?

With no output schema, the description carries some burden for explaining the return payload, and it does not (e.g., decoded call structure, signature output). For a one-input read-only decoder this is adequate but incomplete, since neither the input format nor the output shape is described.

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?

There is a single parameter (data) with 0% schema description coverage, and the description does not compensate by specifying the expected format (hex string, 0x-prefix, byte length). The agent must guess the input encoding, which is a real gap for a decoder tool.

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?

States a specific verb (decode) and resource (Safe execTransaction and MultiSend batch calldata), plus the notable extras of signature types and per-inner-call decoding. It is clearly narrower than the generic siblings decode_calldata/decode_transaction, though it never names those alternatives explicitly.

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?

Usage is implied by the Safe/MultiSend scope: an agent can infer it should be used when the payload is Safe-specific calldata. There is no explicit 'use this when / use X instead' routing or mention of prerequisites, so guidance remains inferred rather than stated.

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