get_linkedin_profile

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It reveals that the operation is a read ('Get') and scoped to the authenticated user, but it does not mention response shape, potential errors, authentication requirements beyond the implicit scope, or any limits. The description is accurate but minimally transparent.

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 entire description is one efficient sentence with no filler. The key verb, scope, and resource are all front-loaded, making it easy for an agent to parse quickly.

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, parameterless getter, the description provides enough information to know what the tool does and for whom. It lacks an explicit explanation of what 'profile information' includes, and there is no output schema to fill that gap, but the overall context is sufficient for basic tool selection and invocation.

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?

The tool has zero parameters, so there is no parameter ambiguity to resolve. The schemas provide 100% coverage of the empty parameter set, and the description correctly focuses on the result rather than parameter details. Baseline 4 for a parameterless tool is appropriate.

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 identifies the action ('Get'), the resource ('LinkedIn profile information'), and the scope ('authenticated user's'). It is immediately distinguishable from siblings like get_linkedin_posts and get_linkedin_connections, which target different resources.

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 phrase 'authenticated user's' implies this tool is for the caller's own profile, not for general people search. However, it never explicitly contrasts with search_linkedin_people or other profile-related siblings, leaving the routing decision mostly to inference.

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