m2m_get_dex_liquidity

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

With no annotations, the description carries the full burden of behavioral disclosure. 'Return' implies a read operation, and 'tracked' hints at data scope, but the description does not explain whether the pair parameter is required, how missing or unknown pairs are handled, or what data freshness or authentication constraints apply.

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 a single, front-loaded sentence with no filler. It loses a point for the ambiguous 'tracked' qualifier, but overall it is compact and easy to parse.

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?

There is no output schema, no annotations, and the description does not cover the parameter format or return shape. For a one-parameter tool this is still below the minimum viable level because the 'pair' input is entirely undocumented.

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 only parameter, 'pair', has 0% schema description coverage, and the tool description never mentions it. The agent is left without knowing whether 'pair' is an address, a token symbol pair like 'WETH/USDC', or a pool name.

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 names a concrete verb ('Return'), a specific resource ('tracked Base DEX pool reserve and liquidity metrics'), and a domain (Base DEX pools). It is reasonably clear, though it does not differentiate itself from the sibling 'get_dex_metrics' tool by name.

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 about when to use this tool instead of related tools such as get_dex_metrics or m2m_get_token_price. No context, exclusions, or prerequisites are provided, so the agent must infer the appropriate use case from the name alone.

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