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

With no annotations, the description must carry the full behavioral burden. It usefully discloses the sort order (volume then transaction count) and the hard cap of 20 results, which are behavioral traits not present in the schema. It does not state that this is a read-only operation, nor does it mention data freshness, auth requirements, or rate limits.

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?

Two short sentences with zero filler; the resource and ranking criteria come first, followed by the limit constraint. Every clause carries information the agent needs.

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?

An output schema exists, so return values need not be explained. For a simple one-parameter read tool, the description covers what is returned, how it is ranked, and the result cap, which is sufficient to call it correctly; only permission/read-only context 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 0% for the single 'limit' parameter, so the description must compensate, and it does add a real constraint ('max 20') that is absent from the schema (no maximum is defined). It does not restate the default of 5, but the added bound is the more important piece of information.

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 names a specific resource (on-chain autonomous agents on Base) and states the ranking criteria (USDC transaction volume and transaction count), which is a clear verb+resource statement. It does not explicitly differentiate itself from siblings like get_agent_liveness or get_reputation_summary, but the resource is distinct enough that an agent can distinguish it.

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 term 'trending/most active' implies a discovery use case, and the ranking criteria hint at what the result is good for. However, there is no explicit when-to-use guidance, no mention of when not to use it, and no pointer to alternatives such as get_reputation_summary or get_agent_liveness.

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