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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds the account-owner scope and states that the operation reads the personal network. It does not mention pagination behavior, rate limits, or what happens when multiple accounts exist, but the annotations lower the burden.

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 three sentences with no wasted words: it states the operation and resource, gives concrete use cases, and clarifies scope. It does not repeat the schema or annotations and is easy to scan.

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 list/search tool with strong safety annotations, the core purpose and context are clear. However, search semantics and cursor pagination are left implicit, and there is no mention of behavior with multiple connected accounts beyond what the schema's account_id description provides. An agent could likely invoke it, but not with complete confidence about search and pagination.

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 description coverage is only 33%: only account_id has documentation in the schema, while cursor and search have no descriptions. The tool description says 'List/search' but does not explain how the search parameter matches (name, company, title, etc.) or how cursor pagination works. With such low schema coverage, the description needed to compensate and does not.

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 operation ('List/search') and the resource ('the LinkedIn connections of the account owner'), and adds representative use cases. It also distinguishes the data domain from company pages, though it does not explicitly name a sibling alternative such as linkedin_list_user_relations or linkedin_search_people.

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 explicitly enumerates question types where this tool is appropriate, such as 'who do I know at this company?' and 'find Sarah in my network'. It clarifies that this reads the personal network rather than a company page, but it does not provide exclusions or direct agents to alternative tools.

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