social_media_posting_start_linkedin_oauth

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the description need not repeat those. However, it adds no behavioral context beyond 'starts OAuth' — it doesn't mention the flow's outcome, whether a URL is returned, or any external side effects. The description carries little additional value beyond annotations.

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, concise sentence with no fluff. It gets to the point, but it is so brief that it borders on under-specification. Still, it is efficiently written for the purpose it conveys.

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 4 parameters and no output schema, the description leaves out critical details: what each optional parameter (Page, Reconnect) means, what the expected response is (e.g., a URL), and how to complete the OAuth flow. The context of many sibling tools also demands more differentiation. The description is insufficient for an agent to confidently invoke without additional research.

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 descriptions cover 100% of parameters (Page, User Id, Reconnect, Location Id), so the baseline is 3. The description adds no further parameter meaning, and the schema descriptions themselves are minimal ('Page', 'Reconnect' are ambiguous), but the description does not help clarify them.

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 'Starts OAuth For LinkedIn Account' clearly states a specific action (starts OAuth) on a specific resource (LinkedIn account). It distinguishes from other platform OAuth tools by naming LinkedIn. However, it does not distinguish from related LinkedIn tools like attaching a profile, relying on the name for that.

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?

No guidance is provided on when to use this tool versus the many sibling OAuth start tools (Facebook, Google, etc.) or the attach_linkedin resource. It does not indicate prerequisites, whether a user must be authorized, or if reconnect should be used. The agent is left to infer usage.

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