paybot_list_networks_and_tokens

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

With no annotations, the description carries the full behavioral burden and does well: it discloses read-only/offline operation, no API-key requirement, and a meaningful data-visibility constraint ('only the PUBLIC open-core registry — operator-private mainnet addresses are never shown'). It does not describe the shape of the returned data, which is the main remaining gap.

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, front-loaded with the purpose, then operational characteristics, then the scoping caveat. Each sentence adds distinct value with no filler.

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 simple, zero-parameter discovery tool this is nearly complete: purpose, safety/auth profile, and visibility limits are all covered. The one omission is any hint about the return shape (no output schema exists), which an agent might want before consuming the result.

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 there is nothing to disambiguate and the baseline of 4 applies. The description correctly does not waste space describing nonexistent inputs.

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 ('List') and resource ('the networks and tokens PayBot supports') with a clear scope. None of the sibling tools (balance, pay, history, pool_*, etc.) overlap with this discovery function, so an agent can distinguish it immediately.

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 purpose implies the usage context (discovering supported networks/tokens), and 'read-only, offline, requires no API key' tells the agent this is cheap and safe to call freely. However, it never explicitly says when to reach for this versus siblings like paybot_pay or paybot_balance, nor does it name an alternative.

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