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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so safety is covered. The description adds genuinely non-obvious behavior: it is public/unauthenticated ('No API key required'), returns specs without user profitability data, and folds the Goldshell HS-Lite dual-mode device into a single row (`hs-lite`), which affects how results should be interpreted.

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 correctly with endpoint and the key scoping clause. The trailing enumeration of every algorithm family and the per-SKU note about HS-Lite is dense and partly redundant for selecting the tool, though it does help an agent recognize whether a given coin is covered.

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 zero parameters and no output schema, the description responsibly says what the payload covers (specs, not profitability) and which algo families appear, which substitutes for the missing return-value documentation. It could still note the response shape (list of rows, field of machine IDs) but nothing essential to calling it is missing.

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, so there is nothing for the description to disambiguate; baseline 4 applies. The description instead spends its budget on what the fixed result set contains, which is the relevant semantics for a zero-arg call.

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 concrete resource and scope: 'public ASIC catalog (specs only, no user profitability)'. This distinguishes it in spirit from the user-centric sibling list_miners/get_rigs, but never names those siblings explicitly, so the differentiation is inferred rather than stated.

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?

Implied usage comes through the 'specs only, no user profitability' and 'no API key required' framing, which hints this is the anonymous lookup path versus a personalized listing. However, there is no explicit when-to-use statement and no alternative named among the many siblings (list_miners, get_rigs, calculate_profitability).

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