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

Annotations already declare readOnlyHint and openWorldHint, so safety is covered. The description adds meaningful behavioral context beyond annotations: it discloses that calls cost 1 credit, lists the returned fields, and notes applicability to school and showcase pages. It does not discuss caching despite the cache_max_age parameter.

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 two tight sentences with return fields front-loaded and cost appended. The initial fragment 'Company page.' is slightly redundant with the title but does not waste much space.

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?

Because there is no output schema, the description appropriately lists the data fields returned, and it covers credit cost and page-type scope. However, it leaves the cache_max_age parameter unexplained and gives no routing guidance among the many LinkedIn sibling tools, so a few gaps remain for an agent to resolve.

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 only 50%: url is documented in the schema, but cache_max_age has no description in either the schema or the tool description. The description adds no parameter-level meaning (e.g., accepted URL forms or what cache_max_age controls), so it does not compensate for the coverage gap.

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 this retrieves a LinkedIn company page and enumerates the fields returned (description, industry, followers, etc.). It also notes it works for school and showcase pages, which helps distinguish it from linkedin_profile, but it does not explicitly contrast with nearby siblings like linkedin_companyPosts or linkedin_searchPosts.

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?

Usage is implied by the resource name and the scope note about school/showcase pages, but there is no explicit when-to-use guidance or named alternative for company posts, people profiles, or post search. An agent must infer from sibling names that this is the right tool for page metadata.

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