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

With no annotations, the description must carry the behavioral disclosure burden. It implies a read-only operation by calling it 'metadata' and mentions 'CoinGecko' as a data source, giving some insight into external API usage. However, it does not disclose behavior on invalid inputs, possible latency, rate limits, or what happens when a coin is not found.

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 concise, with no fluff, and front-loads the tool's purpose. However, it is so terse that it omits essential usage information. While brevity is good, it sacrifices clarity around input and usage, making it minimally acceptable rather than well-structured.

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 that the tool has an output schema, the description need not explain return values. However, for a 1-parameter tool with no explanatory annotations, it should at least clarify the purpose of 'q' and any constraints. It also does not distinguish itself from similar crypto tools. The description is inadequate for an agent to call it correctly without external assumptions.

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 schema has one parameter 'q' with zero schema description coverage. The description does not explain what 'q' should contain (coin name, symbol, ID), its format, or any constraints. It adds no meaning beyond the schema's property name, leaving the agent to guess the required input.

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 identifies the tool as providing coin metadata (categories, algorithm, genesis) from CoinGecko. This is specific enough to differentiate it from price-focused siblings like cryptoprice and cryptomarket, though it does not use a verb like 'get' or 'retrieve'. The resource and key fields are clear.

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 provides no guidance on when to use this tool over alternatives, no expected input format for 'q', and no mention of limitations or exclusions. It does not help an agent decide whether to use coininfo versus crypto or cryptomarket. There is no usage context whatsoever.

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