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

Annotations already declare readOnlyHint=true and openWorldHint=false. The description adds useful behavioral context: the score is z-scored against a trailing decade, updates weekly, and includes fields like trend and top_partners. It does not discuss error behavior or authentication, but for a read-only analytics tool the provided transparency is adequate.

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 description is two sentences: the first explains what is returned and how it is calculated, the second provides usage triggers and update frequency. It is information-dense with no filler, front-loading the purpose.

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, the description enumerates the key returned fields (trend, z_score, latest_hhi_0_10000, latest_total_imports_usd, top_partners), explains the data source and methodology, and provides usage guidance. The single parameter is fully documented in the schema, making the description complete for this low-complexity tool.

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 schema provides 100% coverage for the single optional parameter 'days' with a clear description, minimum/maximum, and fallback behavior. The tool description does not add any extra parameter explanation, so the baseline of 3 applies.

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 explicitly states the tool returns a 0-100 US pharmaceutical import-concentration score, specifies the calculation (annual HHI of HS 3004 medicament imports by partner country, UN Comtrade, z-scored), and names the output fields. This clearly identifies the resource and differentiates it from generic database or scoring tools.

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?

The description gives explicit call conditions: 'Call when the user asks about drug-supply concentration, pharma sourcing fragility, shortage or COGS-shock exposure, or supplier-country dependence, or when timing formulary diversification, safety-stock, or supplier-contract decisions.' It does not explicitly mention when not to use or name alternatives, but the context is clear and actionable.

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