linkedin_auth

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

With no annotations, description fully discloses opening a browser window, saving the token, and its 2-month lifespan, giving complete behavioral context.

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?

Three concise sentences, each essential: authentication method, prerequisite, and token lifetime. No unnecessary 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?

Given zero parameters and presence of output schema, description covers all essential aspects: OAuth mechanism, ordering constraint, persistence, and expiration. Complete for an auth tool.

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?

No parameters exist, so no additional meaning needed beyond schema. Baseline 4 for 0-param tools; description adds value by explaining behavior instead.

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?

Description clearly states the tool authenticates with LinkedIn via OAuth 2.0, a specific verb-resource pair. It distinguishes from sibling tools (profile, posts, stats) that require prior authentication.

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?

Explicitly says 'Must be called BEFORE any other LinkedIn tool if the user is not yet authenticated' and notes it only needs to be run once, providing clear when-to-use and persistence guidance.

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