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

Annotations already declare readOnly, idempotent, and non-destructive behavior. The description adds meaningful behavioral/access context beyond annotations: the call costs $0.10, supports prepaid x-credit-token headers, includes a free tier, needs no wallet or API key, and returns an auditable receipt.

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 dense but front-loaded with the core verdict and purpose. It covers purpose, constituent checks, pricing, authentication, and output in a compact form; minor promotional phrasing like 'This is the tool to bind first' is not harmful but adds little.

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 tool with an output schema and full parameter documentation, the description is complete: it explains why to call it, what it evaluates, what output to expect, how billing works, and what access prerequisites exist. No critical selection or invocation information is missing.

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 100%, so both parameters are already documented. The description only restates that address is required and does not add new meaning about amountUsd or parameter formatting, so it adds no significant value beyond the schema.

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 the tool produces a GO/HOLD/STOP verdict combining token risk, sellability, route/price-impact, and deployer reputation for a Base token. It identifies the resource and outcome, but the verb is implicit ('one call before you trade') rather than a specific action like 'returns' or 'evaluates'.

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: use this before trading a Base token and 'bind first' for pre-trade assessment. It also positions itself as cheaper than doing four separate checks à la carte, but it does not explicitly name sibling alternatives or state when not to use it.

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