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

With no annotations, the description carries full burden. It transparently discloses the data quality issue (key_suppliers only ~58% filled) and clarifies the meaning of the country field, preventing misinterpretation. No mention of destructive behavior or rate limits, but those are not relevant here.

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 front-loaded with the core purpose and each sentence adds value (behavioral caveats, clarification on country). It is slightly verbose but still efficient. A minor trim could improve conciseness.

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?

Given no output schema, the description fully explains the return values (HHI, supplier_edge_coverage, most concentrated bucket) and adds necessary context about data coverage. For a single-parameter tool, this is comprehensive and leaves no ambiguity.

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 coverage is 100% with a single parameter described as 'Focal company id (snake_case, e.g. 'tsmc') or exact company name.' The description reiterates this but adds no new semantics beyond what the schema already provides. Baseline 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 specifies the verb 'break down and report', the resource 'suppliers of a focal company', and the results (HHI by country/segment, most concentrated bucket). This clearly distinguishes it from sibling tools like find_consolidation_hotspots or find_single_source_dependencies.

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 includes important caveats: supplier_edge_coverage is always reported due to data sparsity, and the country field refers to headquarters not manufacturing. It implies use when concentration analysis is needed, but does not explicitly state when not to use or list alternatives.

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