ghl_ad_li_current_user_get

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false. The description adds endpoint details and OAuth scopes (adPublishing.readonly) but does not describe side effects beyond what annotations imply. No contradiction.

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 four lines, concise, and well-structured. It includes endpoint, version header, and OAuth scopes. Every sentence adds value, with no redundancy.

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 simple read operation with only 2 parameters, the description is adequate but lacks details on return values or examples. Annotations cover safety. Could be improved with a note about the response format.

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?

Input schema covers 100% of parameters with descriptions (locationId, isDraft). The description does not add any additional meaning beyond the schema. Baseline 3.

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 'Get current LinkedIn user' and specifies it retrieves authenticated user info for a location. The endpoint and OAuth scopes are provided, distinguishing it from sibling tools like ghl_ad_google_current_user_get and ghl_ad_fb_current_user_get.

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 does not explicitly compare to alternatives, but the tool name and description indicate it is for LinkedIn. Sibling tools for other platforms exist, and the description implies when to use this tool (when LinkedIn user info is needed). Lack of explicit exclusion of other tools.

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