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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the description does not need to restate safety. It adds the scope ('managed by the connected user') and the output's role in resolving post_as, which is useful context, but it does not disclose return format, pagination, or provider-specific behavior. This is adequate but not rich.

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 short sentences, front-loaded with the operation and followed by the key use case. There is no filler or repetition of schema/annotation content.

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 read-only list operation with zero required parameters and rich annotations, the description provides enough context to call it correctly and explains why the returned pages matter (resolving post_as). It does not enumerate the exact response shape, but the absence of an output schema is mitigated by the simplicity and the stated purpose.

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 optional parameter is fully documented in the schema (100% coverage), including when to omit it and how to disambiguate multiple accounts. The description itself adds no parameter-level detail, so it stays at the schema-backed baseline.

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 and resource ('List LinkedIn company pages managed by the connected user') and clarifies scope, distinguishing it from generic company lookup tools like linkedin_get_company and linkedin_search_companies. It also states the downstream purpose, which removes ambiguity about what this tool is for.

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 gives explicit timing/context: 'Use before publishing as a company page so you can resolve the required post_as company ID.' It does not explicitly list when-not-to-use or alternatives, but the stated use case is clear enough for an agent to select it appropriately among LinkedIn siblings.

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