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

Annotations already declare readOnly and openWorld, so the safety profile is covered. The description adds one genuinely useful behavioral fact — real prices are distinguished from model output, which is explicitly labelled as an estimate — but says nothing about refresh cadence, units, or how the 'most disrupted chokepoint' is chosen when there are no parameters.

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 sentences, front-loaded with what is returned and followed by the trigger condition. Dense with domain jargon ('Kraken BTC/ETH', 'NY Harbor ULSD') but every clause carries meaning.

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 annotations gaps, and no output schema, the description must carry the return-shape burden. It names the instruments and the estimate labelling but not the structure, timeframe, or freshness of the data, leaving an agent guessing what it will actually receive.

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?

There are zero parameters, so the baseline is 4. The description usefully explains the implicit selection rule (it operates on 'the most disrupted chokepoint'), which is information the empty schema cannot convey.

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 specific resource it returns: chokepoint-linked Brent, NY Harbor ULSD, and Kraken BTC/ETH prices plus GeoQuant model direction/strength. That is more precise than the title, though it never states the time horizon or whether it covers one chokepoint or all of 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?

It gives an explicit trigger — 'call this when you need to translate a supply event into likely price pressure' — which is a clear use case. It stops short of naming alternatives (get_market, get_hormuz, get_geo_energy_flows) or saying when a plain price feed is preferable.

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