List the LinkedIn company Pages this account administers

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

Beyond the readOnlyHint annotation, the description adds rich behavioral context: it details the return fields (id, name, role), the empty-case interpretation, and the policy that Hermoso never chooses the page for the user. It also notes the 'free' nature and the possibility of missing organization scopes, which is not covered by annotations.

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 concise and efficient: the primary purpose is front-loaded, followed by a critical usage directive and empty-case handling, with no redundant sentences. Every sentence adds value.

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 read-only list tool, the description is fully complete. It covers the return shape, when to call it, what an empty result means, and how to respond. No output schema exists, but the described return fields suffice.

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?

There are zero parameters, so the description correctly provides no parameter-level detail. Baseline 4 applies since the schema is empty and the description does not need to compensate for undocumented params.

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 verb 'List', the resource 'LinkedIn COMPANY PAGES', and the specific output (id, name, role). It explicitly differentiates from the sibling post_to_linkedin_page by mandating this call before publishing when multiple pages exist, making the purpose unambiguous.

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 when-to-use instructions ('ALWAYS call this before post_to_linkedin_page when there is more than one Page'), explains the empty-return meaning (no admin role or missing scopes), and advises against guessing IDs. This fully routes the agent to the correct behavior.

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