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

With no annotations provided, the description bears the full burden of behavioral disclosure. It does state that the tool returns all coins with their symbol, name, and category, and mentions that new coins are added regularly (data changes over time). However, it omits potential behavioral details such as pagination, sort order, or whether inactive/removed coins are included, which could affect how an agent interprets the output.

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?

The description is three short sentences, each providing useful information: the action and output fields, the update cadence, and the data source. It is front-loaded with the primary purpose and contains no filler or repetition.

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?

Given the tool's low complexity (zero parameters, no output schema), the description is sufficiently complete. It explains what the tool does, what data is returned, and the source. There is no need for further detail about return format or parameters because none exist.

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 has zero parameters, so the baseline is 4. The description does not need to explain parameter semantics, but it adds value by describing the data fields returned, which is sufficient for a parameterless tool.

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 the tool lists all cryptocurrencies evaluated by True Value Rankings, specifying the returned fields (symbol, name, category). This distinguishes it from siblings like get_top_ranked (which focuses on top-ranked coins) and get_tvr_score (which likely focuses on a single coin's score). The verb 'lists' is specific and the resource is well-defined.

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 description implies usage for obtaining the full list of coins, but it does not explicitly contrast with alternatives such as get_top_ranked or get_full_breakdown. There is no clear 'when to use this vs. other tools' guidance, though the phrase 'Lists all cryptocurrencies' strongly implies this is the general listing tool. The statement 'New coins are added regularly' provides minor context about data freshness but no usage exclusions.

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