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

Annotations already declare readOnlyHint, destructiveHint=false and openWorldHint, so the bar is lower. The description adds real context beyond them: the data is model-generated from live market inputs, NiceHash revenue is null when no market rate exists, and results vary with difficulty, coin price, power cost and hardware — all useful for interpreting output.

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 first sentence is well front-loaded and informative, but roughly half the text is repeated legal boilerplate ('estimates only, not investment, financial, or tax advice... not ROI guarantees... Do your own research') that adds no operational value for an agent and dilutes the useful content.

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 parameters, no output schema, and safety fully covered by annotations, the description carries the remaining burden of telling the agent what comes back; it does so (per-unit yield estimates, NiceHash USD/day with null semantics, estimate provenance). Only the authentication/empty-list behavior is left implicit.

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?

Zero parameters, so the baseline of 4 applies. The description correctly adds no parameter discussion and instead spends its words on what the response contains.

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 and resource: fetching the signed-in API-key owner's saved 'My Rigs' list, with per-unit yield estimates. It implicitly distinguishes itself from catalog-shaped siblings like list_catalog_miners and list_miners by scoping to the owner's saved rigs, but never names an alternative explicitly.

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?

Usage is only implied: 'the signed-in API-key owner's saved My Rigs list' tells an agent this is a personal-scope read, but there is no explicit when-to-use, no conditions, and no routing to siblings such as calculate_profitability or list_miners for other data.

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