Login to LinkedIn via OAuth

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

With no meaningful annotation guidance, the description carries full weight. It discloses that the tool opens a browser, captures the callback, exchanges the authorization code, and saves the token to the config file. It also mentions the return value and prerequisites, giving the agent a clear model of side effects and persistence behavior.

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 well-structured with a summary, prerequisites, args, and return value, and it front-loads the core purpose. It is more verbose than strictly necessary because the Args section duplicates the schema, but the extra context about prerequisites and token persistence earns its place.

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 an OAuth login tool with three optional parameters and no output schema, this description is complete. It explains the flow, side effects, prerequisites, parameter behavior, and what the caller receives. An agent can invoke this tool and understand the downstream consequence for all other tools without further guessing.

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 100%, so the schema already documents all parameters. The Args section mostly repeats the schema's names, ranges, defaults, and meanings, adding little beyond the schema. The only marginal addition is 'Set false for headless,' which is already effectively captured in the schema description.

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 and resource: 'Authenticate with LinkedIn using OAuth PKCE flow.' It further describes the end-to-end process, making it unmistakably distinct from the sibling data-operation tools like linkedin_create_post or linkedin_get_my_profile.

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 clearly frames this as the recommended authentication step and notes that 'all other tools can use the saved token automatically,' which establishes when to use it. It also lists the required prerequisites. It does not explicitly name alternatives or exclusion conditions, but the context strongly implies this is the entry point for all other tools.

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