get_hashprice

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

With no annotations, the description carries the behavioral burden, and it does disclose that the value is current-snapshot and comes with a 'detailed breakdown'. It does not say whether data is cached, how fresh it is, or what the breakdown comprises, which is a gap for a read tool with zero annotation support.

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?

A single front-loaded sentence with no filler; the metric definition is parenthetical and tightly scoped. It could arguably be a touch more informative without losing brevity, but nothing is wasted.

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?

There is no output schema, so the description should ideally characterize the 'detailed breakdown' it promises — what fields or dimensions the agent will receive. As written, an agent knows what the number means but not what the payload looks like, leaving the return shape underspecified.

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 no schema semantics to add beyond; the baseline for a zero-parameter tool applies. The description uses the sentence space instead on defining the returned metric, which is reasonable.

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?

Specific verb ('Get') plus resource ('hashprice') with an inline definition of the metric and its unit (mining revenue per PH/day). It is distinguishable from siblings like get_market_data or calculate_profitability by domain specificity, though it never explicitly contrasts itself with 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?

No statement of when to use this versus related tools such as get_market_data or calculate_profitability, and no prerequisites or context. The 'current' qualifier hints at a now-focused snapshot but is not framed as guidance.

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