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

With no annotations, the description carries full burden. It does useful work by disclosing that the value is live ('moves as providers join and hirers ask'), derived from an oracle rule over 24 h hire intents, and framed as a read. It stops short of stating read-only guarantees, caching/freshness semantics, or what consumers do with the returned rate.

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 on the payload and roughly three short sentences with no filler. The middle clause packs several concepts (supply bonus, demand, hire intents, oracle rule) densely, 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?

With no output schema and no annotations, the description must carry the return semantics, and it does: resource kinds, per-kind live rates, the supply×demand derivation, and the 24 h window. It is complete enough for a zero-parameter read tool, with only freshness/precision details left unspecified.

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 4 applies. No misleading parameter claims are made.

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 names the resource (usable resources per kind: rpc, gpu, fpga, storage, ip) and the payload (the live rate each pays), so the agent knows this surfaces grid pool supply and pricing. It does not name a verb or distinguish itself from near-neighbours like taifoon_grid_prices, grid_economics, or grid_status, leaving the agent to infer the boundary.

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?

One implicit directive is given: 'Read before joining to earn most.' That is a usable trigger, but there is no when-not guidance and no named alternative among the many pricing/status siblings (grid_prices, pool_quote, grid_status). Usage is implied rather than explicit.

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