complete_linkedin_connection

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

No annotations are provided, so the description must carry the full burden of behavioral disclosure. It indicates a state-changing operation ('complete') but gives no details on prerequisites beyond timing, potential side effects, error conditions, or what the function returns. For an OAuth completion step, an agent might need to know whether it can be called multiple times, what happens if called before authorization, or how to handle failures. This is a significant gap.

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, front-loaded sentence with zero wasted words. It places the essential condition ('after authorization in the browser') right at the start. Every word contributes to the meaning.

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 0-parameter tool with no output schema, the description covers the essential usage timing but omits other operational context. It does not explain the return value (which could be critical for the agent to know whether the connection succeeded), nor does it note any prerequisites beyond the browser step. The lack of an output schema raises the burden on the description to describe the result, which it fails to do. Still, given the simplicity, it is minimally adequate.

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 the schema is trivially 100% covered. Per the calibration guidance, a 0-parameter tool gets a baseline of 4. The description does not add parameter-specific details (there are none), and that is acceptable because there is nothing to document.

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 completes the LinkedIn OAuth flow after browser authorization. The verb 'complete' and the specific context 'after authorization in the browser' make the purpose unambiguous and distinguishable from sibling tools like start_linkedin_connection, which initiates the flow. It is specific enough for an agent to understand the tool's role, though it does not explicitly name the alternative.

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 provides a usage condition: 'after authorization in the browser' – implying this tool should be called only after the user has completed the browser-based OAuth step. However, it does not explicitly state when NOT to use it or mention alternative tools like start_linkedin_connection. The guidance is implied rather than explicit, so it meets the 'clear context, no exclusions' level.

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