blockrun_dex

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

No annotations are provided, so the description must bear the full burden. It mentions 'real-time' and 'FREE - no payment required', but does not disclose whether the operation is read-only, any rate limits, authentication requirements, or potential side effects. The read-only nature is implied but not explicit.

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 concise, starting with the main purpose, followed by a bullet list of use cases, and then code examples. It is well-structured and front-loaded. Minor redundancy in repeating the same examples for each parameter could be tightened.

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 4 parameters and no output schema, the description provides a good overview and usage context, but lacks details about the return format or response structure. An agent would need to infer what data fields are returned, which is a gap for a data retrieval tool.

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 input schema covers all 4 parameters with descriptions (100% coverage). The description adds value by showing example usage patterns (e.g., { query: 'SOL' }) but does not introduce new parameter meaning beyond what the schema provides. Baseline 3 is appropriate.

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 'Get real-time DEX data from DexScreener', specifying the verb (Get), resource (DEX data), and source. It provides distinct use cases (token prices, liquidity, volume) and examples that differentiate it from siblings like blockrun_price.

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 lists explicit use cases ('Use for: Token prices and liquidity across chains...') and provides concrete examples. However, it lacks explicit guidance on when not to use this tool versus alternatives, such as for simple price checks via blockrun_price.

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