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

With no annotations, the description carries the full burden, and it does disclose genuinely useful operational facts: a $0.01 USDC charge on Base (eip155:8453), payment supplied via `params._meta["x402/payment"]`, and a free /sample. That payment/wallet flow is real context beyond the schema. However, it never states that the tool is read-only, what the call returns, or whether failed/unpaid calls are charged, so the behavioral profile is only partially covered.

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 blurb is front-loaded with a service marketing line and an HTTP URL rather than the tool's function, then devotes sentences to sibling endpoints (/report, /price, /sample). Much of the text does not earn its place for this specific tool, and the one sentence that matters (exit cost) is buried mid-paragraph.

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 are no annotations and no output schema, so the description must define the operation and its result; instead it defines the pricing rails. An agent still does not know what `exit` returns or what the `tokens` argument accepts, which are the two things needed to invoke it correctly.

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% for the single `tokens` string parameter, so the description must explain its format. The only near-relevant mention, "/price now takes up to 10 tokens per call for bulk screening," describes a different endpoint and leaves unclear whether `tokens` here is a comma-separated list, a cap, or a single symbol.

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 text opens with the service-wide slogan "Base token due diligence over x402" and then markets three other endpoints (/report, /price, /sample); the tool's own operation is never stated. The only hint at what this tool does is the phrase "position exit cost" buried inside the /report blurb. An agent must infer that `basedue__exit` computes exit cost for a token position, which is close to tautology-by-name rather than an explicit purpose statement.

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 condition is given for when to call `exit` instead of the sibling tools `basedue__due`, `basedue__price`, or the bundled `basedue__report` — even though the description explicitly advertises the other two endpoints' bulk/combined behavior. The comparative info present steers an agent toward the siblings, not toward this tool.

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