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

No annotations are provided, so the description carries the full behavioral burden. It usefully enumerates what the returned record contains (components, OEM relationships, country, stock code, bottleneck risk, sources), but says nothing about behavior on a missing/invalid slug, authorization needs, or rate limits.

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?

A single front-loaded sentence that leads with the action and identifier before listing the returned fields. The field list is long but each item is a distinct piece of record content, so little is wasted.

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 does the work of telling the agent what comes back, listing the record's contents, and a 1-param read tool needs little more. The main missing piece is failure behavior for an unknown slug and cross-reference to search_suppliers.

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% and the slug parameter already carries concrete examples (harmonic-drive-systems, leaderdrive, nabtesco, catl). The description reinforces that the lookup key is a slug but adds no format, casing, or resolution detail beyond the schema, so the baseline 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?

States a specific verb (get) plus resource (full supplier record) and scopes it to a single supplier identified by slug, which implicitly separates it from the list-style search_suppliers sibling. It never names that sibling explicitly, so the differentiation is inferred rather than stated.

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 'by slug' phrasing implies you must already know the slug, which is mild usage guidance, but the description never says when to reach for this over search_suppliers or that search_suppliers is the way to obtain a slug. No exclusions or prerequisites are given.

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