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

Annotations already cover safety traits (read-only, non-destructive, idempotent, closed-world), so the description only needs to add context. It does so by explaining the ranking metric and that results include when each app was first seen in the index, but it stops short of mentioning result size, freshness limits, or other operational caveats.

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 a single efficient sentence followed by a targeted usage sentence. The ranking basis is front-loaded and no words are wasted.

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 zero-parameter, read-only tool with no output schema, the description gives enough detail to understand what is returned: ranked apps with payment metrics and first-seen timing. It does not clarify result count or pagination, but that is a minor gap rather than a blocker.

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 has zero parameters, so there are no parameter semantics to document. Per the rubric, this baseline is 4.

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 resource (apps on Arc), the time window (last 7 days), and the ranking basis (stablecoin payments received with USD, payments, and new paying wallets). It is specific enough to separate this from generic app-listing siblings, though it does not explicitly name or contrast with tools like arc_new_apps.

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 gives concrete user intents: 'which apps on Arc are most used,' 'which accept USDC,' and 'what is new on Arc.' This is clear usage context, but it does not explicitly state when not to use it or name an alternative tool for overlapping questions.

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