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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds that results are coins and Cryptominium pages (i.e., a discovery/browse surface), which is modest added value, but says nothing about result limits, ranking, or empty-result behavior.

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?

Two sentences, front-loaded with the resource and scope. There is mild redundancy between 'returns the matching coins and Cryptominium pages' and 'find the right Cryptominium page', but no filler beyond that.

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?

For a single-parameter, read-only, open-world search with no output schema, the description covers input flexibility and the general shape of results. Missing only operational detail (ranking, limits, no-match behavior), which is a minor gap at this complexity.

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?

With one parameter and 100% schema coverage, the baseline is 3, but the description goes beyond the schema's terse 'Anything crypto.' by enumerating the query types the parameter accepts (ticker, address, transaction, comparison, question, category), giving the agent concrete guidance on free-text form.

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 ('crypto search') and enumerates the kinds of input it accepts (ticker, address, transaction, comparison, question, directory category), plus what it returns (matching coins and Cryptominium pages). It does not explicitly name the specialized siblings (identify_address, explain_transaction), but the broad-coverage framing implicitly distinguishes it from them.

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?

'Use it to find the right Cryptominium page for a crypto question' gives a positive usage context, but there is no when-not guidance and no mention of the sibling tools (e.g. using identify_address for a specific address instead). The routing decision is left to inference.

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