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

Annotations already declare readOnlyHint=true, openWorldHint=true, and destructiveHint=false, so the safety profile is covered. The description adds context beyond this: it mentions the tool is 'free,' explains the scope requirement ('LinkedIn has not granted this app the organization scopes'), and describes the empty-case behavior. This adds value without contradicting the 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 brief and well-structured. It opens with the core purpose, then provides the critical usage rule, and finishes with the empty-case handling. Every sentence serves a purpose, and the critical guidance is front-loaded.

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 no-parameter, read-only listing tool, this description is complete. It covers what is returned, when to use it, how to handle an empty result, and even mentions scope prerequisites. Nothing an agent needs to correctly invoke this tool is missing.

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 and 100% schema coverage (trivially), so the baseline is 4. The description adds no parameter details (since none exist) but does clarify the output structure (id, name, role), which is useful even though it is not parameter-related.

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 ('List') and resource ('LinkedIn company Pages the account administers'), and specifies the returned fields (id, name, role). It clearly distinguishes from the sibling tool post_to_linkedin_page by referencing it directly, so an agent knows exactly what this tool does and what it does not do.

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?

Explicit usage guidance is given: 'ALWAYS call this before post_to_linkedin_page when there is more than one Page,' with a clear rationale (avoiding public mistakes and that 'Hermoso never chooses for the user'). It also explains what to do if the result is empty (say plainly rather than guessing an id), covering the when-to-use and interpretation aspects.

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