get_dex_metrics

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. Calling this tool an alias reveals nothing about side effects, read-only status, rate limits, or data returned. It provides zero behavioral context.

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 concise sentence with no waste and directly states the alias relationship. However, its brevity contributes to the lack of substantive content, though the dimension rewards efficient expression.

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 annotations, no output schema, and no param explanations, the description must itself provide enough to call the tool correctly. It only points to a sibling noname, without describing what data is returned, how to call it, or any behavioral expectations. This is entirely inadequate on its own.

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 tool takes zero parameters, and the schema is empty. Per the rubric, a tool with no parameters has a baseline of 4; no further param documentation is needed.

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 only states 'Alias for m2m_get_dex_liquidity.' This identifies a relationship to a sibling tool but does not explain what the tool actually does. An agent must infer the behavior from the sibling's name, which is vague and indirect.

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?

No guidance is given about when to use this tool versus the canonical sibling. The alias relationship implies interchangeability, but the description does not explicitly state conditions or contexts. There is no mention of alternatives or exclusions.

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