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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds genuinely non-structured context: the data comes from a 'latest daily scan', telling the agent results may be up to a day stale rather than a live on-chain read — important for interpreting output. It stops short of describing latency, caching, or what happens if a scan is missing.

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?

A single sentence with zero filler that front-loads the scope ('latest daily scan of every NEP-141 token') before enumerating the three returned facts. Nothing is repeated from the title or schema, and every clause earns its place.

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 parameters and no output schema, the description must carry the burden of saying what comes back, and it does: backed count, under-backed tokens with magnitudes, and reasons. The remaining gap is scope of history — whether only the latest scan is available or prior days can be retrieved — which matters for an agent deciding if this tool can answer a trend question.

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 tool takes zero parameters, so the baseline is 4 and there is nothing for the description to disambiguate. The description correctly implies no inputs are needed by framing the result as a fixed, global daily scan.

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 resource and scope: 'the latest daily scan of every NEP-141 token in NEAR Intents', plus the three things it reports (count backed, under-backed amounts, reasons). It is clearly an aggregate/overview tool, which implicitly separates it from the per-token sibling check_backing, but it never names or contrasts with siblings explicitly.

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?

Usage is only implied: 'every NEP-141 token' signals a broad overview use case, versus check_backing for a single token. There is no explicit when-to-use/when-not-to-use statement, no mention of checker_status, and no guidance on whether to call this first before drilling into an individual token.

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