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

Annotations only cover readOnlyHint and openWorldHint, so the description carries the semantic burden and does so well: it discloses the data sources (GoPlus, DeepScreener pool, SWOGE colony traits), that each flag carries its source, and explicitly warns that no_red_flag_found is not a buy signal and unknown stays unknown. It omits cost/latency behavior for the non-quote path.

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?

Front-loads the decision use-case and verdict values in the first clause, then adds sourcing and caveats. It is dense but every sentence is informative; minor redundancy in restating the data-source list.

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 output schema, the description usefully describes the return shape (verdict plus reasons, per-flag source, per-colony observation counts). It is complete enough for correct invocation, though it does not describe failure modes for invalid or non-EVM addresses.

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 coverage is 100% with documented descriptions for both address and quote, so the schema already explains the parameters. The description only hints at the quote path ('without running or paying for it' appears in the schema, not the description), adding little beyond schema baseline.

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?

States a specific verb+resource ('one verdict you can branch on') and enumerates the exact outcome values (red_flags, caution, unknown, no_red_flag_found). It also distinguishes itself from the sibling scan_token by framing itself as the verdict over the same underlying data.

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?

Gives a clear trigger ('Use this when you must decide fast whether an EVM token is worth a closer look') and names scan_token as the tool judging the same data, implying the alternative. It does not explicitly state when to prefer scan_token over this one, so it stops short of full when/when-not routing.

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