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

The description discloses a free trial limit of 5 calls per signed wallet, which gives some insight into usage constraints and authentication requirements. However, it does not mention whether the tool is read-only, any side effects, or other behavioral traits.

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 very brief and to the point, which is concise. However, it is not structured with details or bullets, and reads more like a tagline than a formal tool description.

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 description is extremely incomplete. There is no output schema, no explanation of what the signals contain, no examples, and no context about how the parameters should be used together. This leaves the tool's functionality largely unspecified.

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?

Each parameter has a generic description like 'Chain to process' that simply repeats the parameter name. This provides no meaningful information about expected values, formats, or relationships between the parameters, leaving users guessing about how to fill them in.

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 'On-chain signals.' is vague and does not use a verb to specify the action. It does not clarify what kind of signals are provided, how they are generated, or what the output represents, making it difficult to distinguish from other on-chain related tools.

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. There is no mention of scenarios, comparisons with sibling tools, or conditions that would make this tool the preferred choice.

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