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

The description adds genuinely useful behavior beyond annotations: per-item results with error tracking and no fail-fast on first error. Annotations already cover the safety profile (readOnly, idempotent, non-destructive, openWorld). It does not describe return shape or partial-failure semantics beyond 'error tracking', so a 3 fits.

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?

Two tight, front-loaded sentences. The scope constraint and the key behavioral differentiator (bulk, never stops on first error) are both stated with zero filler.

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 one-parameter bulk reader with a fully documented schema and annotations covering safety, the description supplies the missing non-obvious behavior (per-item error tracking). It lacks explicit routing vs. the singular sibling and any note on response shape, keeping it just under complete.

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 single 'identifiers' parameter already has a 100% coverage schema description listing accepted formats (URLs, slugs, numeric IDs) and the 1–10 range. The description adds no syntax or format detail beyond what the schema provides, so 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 (fetch) and resource (slim company profiles) with a bulk scope of up to 10. It is distinguishable from the singular sibling linkedin_get_company, but the description never names that sibling explicitly, so it stops short of a 5.

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 'up to 10' bulk constraint and 'slim' qualifier imply when to prefer this over the single-get tool, but there is no explicit when-to-use guidance, no conditions for choosing it over linkedin_get_company, and no exclusions stated. Usage is only implied.

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