list_top_agents

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

With no annotations, the description carries the full burden. It does state 'Read-only' and discloses the reputation/tier/confidence basis of the output, but it says nothing about permissions, rate limits, or whether the result set is paginated or exhaustive.

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?

Three short sentences, leading with the usage condition and following with the return characteristics and safety note. Nothing is redundant, though the output characteristics could be woven into one tighter clause.

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?

A one-parameter list tool with no output schema needs to explain what comes back, and the description does name the ranking plus tier and confidence, while also flagging read-only behavior. Only the relationship to the sibling reputation tool is left unaddressed.

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% and the sole 'limit' parameter already documents its range and default, so the description adds no parameter meaning of its own. Baseline 3 applies when the schema does all the work.

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 verb and resource ('Returns top Routex402 sellers ranked by reputation') and states the ranking signal, so an agent can tell it is a discovery/list tool rather than a single-agent lookup. It stops short of naming check_agent_reputation to draw the contrast 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?

It gives a clear triggering condition ('Use when the user wants to find a trustworthy seller'), which is more than most definitions offer. However, it never says when not to use it or points to check_agent_reputation for evaluating a specific seller, so the routing decision is only partly covered.

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