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

With no annotations provided, the description carries the full burden, and it excels at disclosing non-obvious behavior. It warns that volume columns fall into two different kinds that must not be summed, explains that overlay values can legitimately exceed total volume, and states that data refreshes weekly and is dated to Monday. These details prevent two serious misinterpretation errors.

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 front-loaded with purpose and then delivers dense, high-value caveats in a structured way. The volume-column warning and weekly-refresh note are essential and each sentence earns its place. The formatting with clear paragraph separation keeps the warnings scannable despite the length.

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 covers the most dangerous data semantics and lists the volume columns, which compensates partly for the missing output schema. However, it remains incomplete on parameter meaning, especially 'project', and does not describe the exact row shape or default filtering behavior. An agent would still need to infer some usage details.

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?

Schema description coverage is 0%, so the description must compensate for the undocumented parameters. It only hints at 'chain' through 'per chain', while 'project' and 'limit' are never explained. An agent would have to guess what values project accepts and whether limit controls row count in a meaningful way.

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 what the tool reports: which frontend, router, or interface originated on-chain DEX volume, aggregated per contract per chain. It gives a specific resource and scope, but it lacks an explicit action verb like 'get' or 'query' and does not explicitly distinguish itself from the similarly named sibling contract_attribution.

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 gives clear context for when to use the tool: when you need to name the venue behind volume that block explorers leave anonymous. It also provides strong data-handling instructions, such as not summing partition and overlay columns and not presenting weekly data as today's volume. However, it never explicitly mentions alternatives or says when not to use this tool.

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