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

Annotations already declare readOnly, idempotent, and openWorld hints, but the description goes further by exposing unit conventions (BTC/PH/day vs USD/PH/day), clarifying that networkPhs is not a price, and warning against blending asks and clears. This prevents serious misuse.

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 description is dense but every sentence contributes essential clarification on units, field semantics, and common pitfalls. There is no redundancy or fluff despite its length.

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, the description carries the burden of explaining return values. It covers the major fields and caveats, though it does not exhaustively list every possible field. Sufficient for an agent to use the tool correctly.

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 has zero input parameters, so the baseline of 4 applies. The description instead explains the meanings of output fields like `hashprice`, `medianAsk`, and `recovery`, adding value beyond the empty schema.

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?

The description opens with 'Live SHA256 AsicBoost rental market on MiningRigRentals', clearly stating the tool's resource and domain. It distinguishes itself from sibling tools like `get_buying_gauge` or `get_treasuries` by specifying the exact market and platform.

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?

The description provides clear context about what data the tool returns, making it obvious when to use it for rental market information. However, it does not explicitly mention when not to use it or name an alternative, a minor gap.

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