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

Annotations already establish readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so safety is covered. The description goes beyond that by disclosing the structure of the result: 15 commodities, split into primary (mined/refined) and secondary (scrap/recycled), annotated with HS codes. That is genuinely useful framing, though it does not mention output format details, pagination, or that results are static/closed-world.

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 actionable guidance is front-loaded in the first clause, and the rest supports it. The parenthetical enumeration of all 15 commodity names is long and partly duplicates what the output will return, but it does help an agent match loose user phrasing ('rare earths', 'battery scrap') to this tool, so it mostly earns its place.

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?

An output schema exists, so return-value details need not be explained. With annotations covering the safety profile, no parameters to document, and explicit routing guidance, an agent has everything needed to decide to call this tool first and call it with no arguments.

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 the schema carries nothing to misinterpret and the description has no parameter semantics to explain. Baseline 4 applies; no additional parameter context is possible or 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?

States a specific verb and resource (lists the 15 traded commodities MiningBridge tracks) and names exactly what the list contains, including the primary/secondary split and HS codes. It is clearly distinguishable from siblings like get_commodity_snapshot or assess_supply_risk, which consume commodity names rather than enumerate 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?

Gives an explicit when-to-use trigger ('when the user asks which critical minerals, rare earths, battery materials or scrap streams MiningBridge covers') plus a routing rule ('before any other MiningBridge tool if unsure of the commodity name'). This effectively positions it as the discovery/prerequisite call relative to all twelve siblings.

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