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

Annotations already declare readOnlyHint=true, and the description adds useful behavioral context: it explains the score calculation (Herfindahl, z-scored vs trailing decade), lists output fields, and notes the weekly update frequency. There is no contradiction with annotations, and the added detail helps the agent understand what to expect.

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 plus a short update note, skillfully packing the metric definition, output fields, use cases, and freshness. Every sentence earns its place, and the key purpose is front-loaded.

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?

The description is quite complete for a read-only tool: it explains the score, outputs, use cases, and update frequency. The schema covers the 'days' parameter, so the only minor gap is that the default snapshot behavior is not explicitly stated in the description, but that is present in the schema.

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 sole optional parameter 'days' is fully documented in the schema with description, maximum, and tier requirement (Gold tier). The tool description adds no additional parameter semantics, so with 100% schema coverage the baseline score of 3 is appropriate.

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 clearly states the tool returns a 0-100 US chip-import concentration score, defines it as a Herfindahl index of HS 8542 imports, and lists specific output fields. This verb+resource+scope is precise and distinguishes it from the many sibling tools, especially with concrete use cases like supply-chain fragility.

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?

Explicitly tells when to call: 'Call when the user asks about semiconductor supply-chain fragility or US chip-sourcing dependence on Taiwan or Malaysia, or when timing dual-sourcing, buffer-stock, or supplier-qualification decisions.' This is clear context, but it does not mention when-not-to-use or alternative tools, so it falls short of a 5.

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