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

Annotations already cover readOnly, idempotent, and openWorld behavior. The description adds useful context beyond annotations: access is limited to company pages a connected person can report on, and the server's data model is people-centric rather than page-centric. This helps prevent incorrect assumptions about the underlying data source.

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 focused sentences with no wasted words. It front-loads the core action and scope, then adds the key conceptual clarification about publishing from people rather than pages.

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 one-parameter list tool, the description combined with the full schema and annotations is largely complete. It lacks explicit details about the returned shape or identifiers, but the word 'List' and the tool's purpose make the expected result reasonably inferable.

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 profile parameter is already described as 'Profile name or sessionId from list_profiles.' The description mentions 'connected person' but does not add substantial parameter-level meaning beyond what the schema already provides.

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 the LinkedIn company pages a connected person can report on.' It also distinguishes itself from sibling tools by clarifying that 'this server publishes from people, not pages,' preventing confusion with page-centric or post-centric list tools.

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 a clear intended use case: benchmarking team personal profiles against company pages. It does not explicitly name alternative tools or exclusion conditions, but the context provided is enough for an agent to understand when this listing is relevant.

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