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

The description states the server is 'Read-shaped tools only (anything that buys, sells or writes refuses)' and decode is a read-shaped operation, while annotations declare readOnlyHint=false. This is an annotation contradiction. The truncated 'and unwra —' also fails to disclose the full behavior.

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 useful first sentence is front-loaded, but the description then degrades into a truncated fragment ('and unwra —') and unrelated server marketing/listing text. That boilerplate does not help call decode correctly and should be removed.

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?

The tool has no output schema, yet the description does not specify return structure beyond 'function signature and arguments,' error cases, or how to pass calldata. Combined with the annotation contradiction and truncation, the tool description is not complete enough for reliable autonomous invocation.

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?

With zero schema parameters, the baseline is high, and mentioning 'hex calldata blob' adds type information beyond the empty schema. However, the schema uses additionalProperties=true and the description never names the parameter key or expected shape, so an agent cannot reliably construct the invocation.

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 opens with a specific, non-tautological action: 'Decode a hex calldata blob into a function signature and arguments.' Listing recognized standards (ERC-20/721/1155, WETH, Multicall3, Safe) further clarifies scope and separates it from broader Singularity read tools. It does not explicitly name a sibling alternative, so it falls short of a 5.

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?

There is no guidance on when to choose this tool over siblings such as singularityagent__read_contract or singularityagent__transaction, and no when-not-to-use conditions. The 'Read-shaped tools only' line describes the server's refusal policy rather than routing an agent to this tool versus another.

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