linkedin_get_company_page

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only states 'Get information,' which implies a read operation, but does not disclose any potential side effects, authentication requirements, rate limits, or return format peculiarities. This is minimal beyond what the tool name already conveys.

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 a single, front-loaded sentence. It is appropriately brief, includes a practical example, and contains no unnecessary words. It does not repeat schema information or add fluff.

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 simple getter with one parameter and no output schema, the description is minimal but adequate. However, it does not hint at the shape of the returned data (e.g., name, URL, description), leaving the agent uncertain about what information will be provided. Given the absence of an output schema, slightly more detail would improve completeness.

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 input schema already fully describes the only parameter (companyId: 'The LinkedIn company ID'), achieving 100% schema description coverage. The description adds no extra semantic detail about the parameter; the example 'GD Dev Solutions' is an instance rather than a parameter nuance. Baseline 3 applies as the schema does the heavy lifting.

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 clearly states the tool's action ('Get information about a LinkedIn company page') with a concrete resource type. It distinguishes itself from sibling tools like linkedin_get_profile (personal profile) and linkedin_get_company_posts (posts) by focusing on the company page object itself.

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 provides no guidance on when to use this tool versus alternatives. It does not mention exclusions or scenarios where other tools would be more appropriate. The example company name is illustrative but does not replace explicit usage direction.

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