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

With no annotations, the description does useful work by disclosing the $0.01 USDC cost, Base network, x402 payment location in `params._meta["x402/payment"]`, and HTTP GET endpoint. However, it omits what the tool returns, whether it is read-only, and any response or error behavior.

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 reasonably compact and puts the endpoint and payment details in view, but it spends significant space on sibling endpoint `/report` and `/price` features instead of front-loading the purpose of this specific tool.

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?

For a simple one-parameter tool with no output schema and no annotations, the description still leaves the core operation undefined and the `tokens` input format unexplained. It provides billing mechanics but not enough information to confidently invoke the 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 schema has one optional `tokens` string with 0% description coverage, and the description does not explain the expected format or semantics for this tool. The mention of 'up to 10 tokens' applies to `/price` bulk screening, leaving `basedue__due`'s parameter meaning unclear.

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 opens with the vague phrase 'Base token due diligence over x402' but never states what the `basedue__due` operation itself specifically does. It mostly advertises the `/report` and `/price` siblings, so an agent cannot tell this tool apart from `basedue__report`, `basedue__price`, or `basedue__exit`.

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?

It mentions that `/report` bundles checks and `/price` supports bulk screening, but gives no when-to-use guidance for `basedue__due` versus those sibling tools. The pricing and free-sample notes are commercial context, not selection criteria.

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