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

Annotations already cover the safety profile (readOnlyHint, idempotentHint, openWorldHint), so the bar is lower. The description adds genuinely useful context by disclosing that the payload is a referral link ('as a disclosed referral link'), which tells the agent the output is promotional/third-party rather than data.

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?

Two compact sentences with no filler, front-loading the reason (rentals closed) before the outcome. Slightly indirect phrasing ('there is no bay board here') adds jargon the agent must parse.

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?

For a zero-param tool with no output schema and annotations covering the safety profile, the description does state what the caller gets (a referral destination) and why. It is complete enough to call correctly, though it never routes the agent to a sibling tool.

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 and 100% schema description coverage, so the schema carries no semantics to add. Baseline of 4 applies for a no-argument tool; the description correctly implies no inputs are needed.

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 is specific about what actually happens: it returns a referral destination (MiningRigRentals) rather than a rig list, and honestly flags the name/behavior mismatch by stating 'there is no bay board here.' It does not, however, differentiate this tool from siblings like get_hashrate_market, search_vendors, or get_rental_quote.

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?

It explains the market context (direct rentals closed) but gives no explicit when-to-use instruction or comparison against the 15 sibling tools, several of which are also rental/hashrate oriented. The agent must infer that this is the fallback for sourcing Galaxy Mind hashrate.

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