linkedin_exchange_authorization_code

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

Annotations already indicate this is a write operation (readOnlyHint=false) and non-destructive. The description adds the useful side-effect that the token is stored locally, but it does not cover other behavioral details such as network interaction consequences or whether existing stored tokens are overwritten.

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?

A single, well-front-loaded sentence communicates the core action and the local-storage side effect with no wasted words.

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?

With no output schema and minimal annotations, the description leaves important context unstated: how the authorization code is obtained, what the result looks like, whether existing tokens are replaced, and the relationship to the sibling OAuth flow tool. An agent can call it correctly only by relying on OAuth domain knowledge.

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?

Only one of five parameters has a schema description, and the tool description does not compensate by explaining client_id, client_secret, redirect_uri, or code beyond their names. The description adds little meaning beyond what an agent can infer from standard OAuth parameter names.

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?

States a specific verb and resource: exchanging a LinkedIn OAuth authorization code for tokens. It clearly distinguishes itself from the sibling linkedin_start_oauth_flow by focusing on the code-exchange step rather than flow initiation.

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 term 'authorization code' implies this tool is used after the OAuth flow has produced a code, but the description does not explicitly say when to use it versus siblings like linkedin_start_oauth_flow or linkedin_auth_status. Usage context is implied rather than stated.

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