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

Annotations already cover read-only and non-destructive status, and the description adds genuinely new context: the data is public and cached, no API key is required, and five named algorithms return null because they have no NiceHash book. Missing only freshness/staleness of the cache, which matters for a 'cached' market snapshot.

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 with the endpoint and resource, then packs units, null cases, auth, and usage scope into three tight sentences with no filler. Slightly dense with algorithm-name enumeration, but every clause carries operational information.

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 no output schema and no parameters, the description supplies what an agent needs: units of the returned rates, which algorithms yield null, auth requirements, and the intended downstream use. Nothing material is left unexplained for a zero-parameter read.

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 zero parameters, so there is nothing for the description to disambiguate. Baseline of 4 applies since the schema is empty and fully consistent with the description.

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?

Names a specific resource (NiceHash algorithm paying rates), the exact endpoint, and the units returned (sat per H/s or Sol/s per day). It also distinguishes itself from pricing/rental tools by stating it is a market snapshot used for My Rigs revenue rather than a rental booking.

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?

Explicitly frames the use case (My Rigs NiceHash revenue in $/day) and excludes one alternative interpretation ('not a rental booking'). It does not name the sibling tool an agent should use for rental pricing, so routing between list_nicehash_rates, list_mrr_rates, and calculate_profitability still requires inference.

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