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

The annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds useful behavioral context by listing the categories of information returned (supply, ATH/ATL, genesis date, etc.), which helps an agent anticipate the tool's scope. It does not mention potential edge cases like unknown tickers, but for a read-only, idempotent lookup this is a minor 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?

The description is two sentences with no filler. The primary action and content scope are front-loaded in the first sentence, and the second sentence provides practical usage examples. Every word earns its place.

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?

The tool has a single required parameter, rich annotations, and no output schema, so the description carries the burden of explaining what the agent can expect. It does that thoroughly by enumerating response categories and giving concrete invocation examples. There is no missing information an agent would need to call this tool correctly.

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%, with the coin parameter already documented as 'Cryptocurrency name or ticker (e.g., 'bitcoin', 'BTC', 'ethereum')'. The description repeats the same examples, adding no new semantic meaning beyond what the schema already provides. This meets the baseline but adds minimal extra value.

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 uses a specific verb phrase ('Get a detailed profile') and names the resource (any cryptocurrency), then enumerates concrete content fields (description, market data, supply, ATH/ATL, genesis date, blockchain, categories, links). The provided natural-language examples ('tell me about bitcoin', 'what is ethereum?') make the tool's role unambiguous and clearly differentiate it from sibling tools like crypto_price or crypto_compare.

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?

It explicitly says 'Use this for' background-information questions and provides several example queries, which gives clear context for when to choose this tool. It does not explicitly name sibling alternatives (crypto_price, crypto_compare, crypto_trending) or state when not to use this tool, but the example queries serve as strong implicit guidance.

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