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

Annotations already declare readOnlyHint=true and openWorldHint=true, covering the safety and external-access profile. The description adds that only 'public' profiles are returned and that identity plus profile details are included, which is useful but modest additional context; return shape is left to the output schema.

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 sentences, zero waste, with the core action and the ID requirement front-loaded before the usage condition. Nothing needs to be trimmed.

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 single-parameter read tool with annotations and an output schema already present, the description covers purpose, input source, and result scope adequately. Only the lack of any sibling routing keeps it from a 5.

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% and the schema only says 'Resource identifier', which is vague. The description meaningfully sharpens this by specifying that it must be the numeric LinkedIn company ID drawn from a URL or search result, adding real meaning over the schema text.

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 uses a specific verb ('Fetch') and resource ('public LinkedIn company profile') keyed on the company ID, so the agent knows exactly what it returns. It does not explicitly differentiate itself from siblings like linkedin_showcase or linkedin_product, so it stops just 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?

It states a clear precondition: 'use this when you already have the numeric ID from a LinkedIn company URL or search result.' That is strong positive guidance, but it names no alternative for the case where the agent does not already have an ID (e.g., a search tool).

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