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

Annotations already cover readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, so the safety profile is fully declared. The description adds useful context beyond that: the data is free, it is a daily snapshot ('today's price range'), and it includes provenance counts (how many sources and hosts list each model). It does not discuss caching or refresh behavior, but the remaining gaps are minor.

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-loaded with 'Free.' and then a single dense sentence enumerating the returned fields, followed by a short note about the frontier basket. No filler, though the middle sentence is long and comma-heavy, which slightly reduces scannability.

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?

With an output schema present, the description need not document return structure, yet it does so helpfully; combined with the read-only annotations and zero parameters, an agent has enough to invoke it correctly. The main omission is any indication of which sibling tool to use for other token-price needs.

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 no parameters (0 params, no required fields), so the baseline is 4. The description correctly implies a parameterless bulk listing rather than a filtered query, which is consistent with the empty schema.

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 what the tool returns: canonical model slugs, ticker codes, source/host counts, and today's min/max input/output prices, plus the frontier basket. It is unambiguous what resource is being listed. However, it never distinguishes itself from close siblings like tokens_board, tokens_fixing, tokens_quotes, or tokens_history, which all deal with the same token-price domain.

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?

There is no when-to-use or when-not-to-use guidance, and no alternative is named. 'Free' hints that cost is not a concern but gives no routing logic. An agent must infer from the name alone whether this is the model catalog versus the board/fixing/quotes siblings.

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