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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety and external-data profile is covered. The description adds only that both datasets arrive 'in one result', which hints at a merged payload, but says nothing about freshness, aggregation level, potential truncation versus calling the two tools separately, or return shape.

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 short sentences with the composite relationship front-loaded and the call condition second. Minor waste in the word 'Synonym', which is imprecise for what is actually an aggregation of two sibling tools rather than an alias.

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 is the only place an agent could learn what a 'geo/energy flow' returns — route identifiers, volumes, price-pressure magnitudes, time horizon — and it gives none of that beyond a loose arrow notation. Adequate to choose the tool, thin for interpreting results.

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 and the schema is empty with additionalProperties=false, so there is no parameter semantics to explain; the baseline applies. The description correctly implies a no-argument, take-everything call.

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 identifies the resource (geo/energy flows) and, more usefully, defines it compositionally as get_chokepoints + get_energy_impact, with a hint at the content ('physical oil routes -> price pressure'). That is enough for an agent to tell it apart from the two siblings it aggregates, though it never says plainly what a 'flow' record contains.

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?

'Call this when you want geo/energy flows together' states the selection condition, and the composite framing implies the inverse (use get_chokepoints or get_energy_impact alone for a single domain). It stops short of explicitly naming that alternative path or any exclusion.

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