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

Annotations already declare read-only, idempotent, non-destructive behavior, so the bar is lower. On top of that the description adds domain-relevant traits: reports show published/free status and structural briefs are free. It does not mention pagination, result volume, or ordering, but the added coverage and pricing context exceed what annotations provide.

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 usage trigger is front-loaded and the filter and status information follows logically. The long enumeration of individual minerals is arguably bloat, but it does help the agent judge topical relevance across many possible queries, 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?

With an output schema present, return values need not be explained, and the description correctly focuses on scope, filters, and free/published status. It is nearly complete; the only gap is absence of explicit disambiguation from the closely related report-reading and report-generating siblings.

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?

Schema description coverage is 100% with two enums, so the schema already documents all four parameters. The description's 'Filter by commodity, depth band or criticality list' largely restates the schema, and its note that structural briefs are free slightly tensions with the schema's "'brief' is free" wording, so it adds only marginal meaning over structured fields.

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 gives a specific verb ('Lists') and a clearly scoped resource ('MiningBridge research reports'), plus the coverage domain (65 minerals across the US 2025 and India 2023 lists). It does not, however, explicitly distinguish itself from siblings like read_report or generate_market_report, so the agent must 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?

It opens with a concrete when-to-use trigger ('when the user asks about the supply chain, mining, processing... of a critical mineral'), which is strong routing context. It stops short of naming alternatives or when-not-to-use conditions (e.g., versus read_report for a single known report), so it is clear but not fully exclusive.

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