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

No annotations exist, so the description carries the disclosure burden; it does describe the returned fields, which is valuable given there is no output schema. However, it is silent on notable behavioral risks: both parameters are optional (required=0) so behavior when neither or both are supplied is unknown, partial-name matching likely returns multiple/none and ambiguity handling is unstated, and there is no mention of auth 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?

Three tight sentences with the core purpose front-loaded and the field enumeration before the use case. Every sentence carries information; only the use-case clause is close to padding for an agent.

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?

For a two-parameter lookup with no output schema and no annotations, the description covers what is returned and why one would call it, which is most of what an agent needs. The remaining gap is identifier disambiguation and ambiguity behavior when partial names match multiple employers.

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%: 'name' already documents English/Chinese and partial matching, and 'company_id' is self-evident. The description adds no guidance on precedence between the two identifiers or how to use them together, so it neither compensates nor detracts. 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 ('retrieve') and resource ('firmographic data on a specific Chinese employer') and enumerates the payload (industry, size tier, ownership type, macro category, employer brand stats). Implicitly positioned as the single-entity lookup against search_companies, but no sibling is named, so differentiation is inferential rather than explicit.

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?

Gives a positive use case ('competitive analysis and compensation benchmarking by employer') but no when-not-to-use, no routing to search_companies for discovery, and no guidance on when to prefer name vs company_id. Usage is implied by the stated scenario rather than prescribed.

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