List the LinkedIn company Pages this account administers

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

Beyond the readOnlyHint and destructiveHint annotations, the description adds meaningful behavioral detail: it lists the returned fields, explains the empty-result meaning (no admin role OR missing organization scopes), and instructs the agent not to guess an id. It also explicitly says 'Read-only, free,' reinforcing the safety profile.

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 compact and front-loaded: it opens with the core purpose, then the critical usage warning, then edge-case handling, and closes with read-only/free status. Every sentence contributes useful information with no redundancy.

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 parameterless list tool, the description fully covers what is returned, when to call it, how to interpret an empty result, and the behavioral guardrail about not guessing an id. The annotations already cover safety, and no output schema exists, so the description carries the needed context well.

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 tool has zero parameters, so there are no parameter semantics to explain. The schema coverage is effectively complete and the description adds no parameter-related detail, which is appropriate for a parameterless tool. Baseline of 4 applies.

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 states a specific verb and resource: 'List the LinkedIn COMPANY PAGES the connected account administers' with the exact returned fields (id, name, role). It clearly stands apart from sibling posting tools like post_to_linkedin_page and list_meta_pages by scoping to LinkedIn company Pages under the connected account.

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 gives an explicit when-to-use rule: 'ALWAYS call this before post_to_linkedin_page when there is more than one Page' and explains the risk. It does not explicitly state when not to use it or compare with alternative listing tools, but it provides a clear operational context and a condition for calling it.

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