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

With no annotations, the description carries the full burden and delivers: 'Reading costs nothing' (cost), 'Requires your Nevermined API key on the Authorization header' (auth), and the non-obvious reconciliation rule for chargedNotDelivered (a failed-but-unreconciled payment is not counted). These are exactly the traits annotations would otherwise supply.

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?

Front-loads the core purpose, then field semantics, then sibling routing, then auth — a sensible order with little waste. The chargedNotDelivered sentence is densely nested and takes a re-read, which keeps it short of perfect.

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?

No output schema exists, so the description must explain return values, and it does for all three fields (total, series shape and ordering, chargedNotDelivered). Auth, cost, and sibling routing are all covered, so an agent has everything needed to call and interpret it.

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%, so `from` and `to` are already fully documented as inclusive ISO-8601 bounds. The description only implies the period concept ('in the period') and adds no syntax or default behavior beyond the schema, so the baseline 3 applies.

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+resource ('Count your Router payment requests') and immediately scopes it against siblings by noting the count is uncapped 'unlike list_payments'. An agent can distinguish this from list_payments and get_budget without opening any schema.

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?

Explicitly routes: use get_budget for 'what has been spent or what is left' and list_payments for 'amounts per payment'. It also gives a behavioral instruction ('flag a non-zero count to the user') for the chargedNotDelivered case, leaving nothing to inference.

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