get_my_connections

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

The description provides no details beyond the basic operation. No annotations exist, so the description carries the full burden. It does not disclose if this is read-only, whether a session is required, or any rate limits.

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 a single sentence, which is concise but lacks important details. It is appropriately front-loaded but too sparse for a tool with no annotations or parameter descriptions.

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?

Despite having an output schema (context signal), the description omits what the output contains, pagination behavior, or prerequisites. The 1-parameter tool is inadequately documented without behavioral or output context.

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 single parameter 'limit' has no description in the schema (0% coverage) and is not explained in the tool description. The agent receives no guidance on what this parameter does or its valid range.

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 tool retrieves 'your LinkedIn connections' via 'CDP browser,' specifying the resource and verb. However, it does not differentiate from sibling tools that also retrieve lists, like get_company_employees or get_sidebar_profiles.

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?

There is no guidance on when to use this tool versus alternatives. With 31 sibling tools including other list-retrieval tools, the lack of usage context is a significant gap.

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