linkedin_profile

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

No annotations are provided, so the description must convey behavioral traits. It states 'Extract' indicating a read operation but does not disclose what data is returned, any limitations, authentication requirements, or error conditions. The lack of output schema further leaves agents unaware of the response format.

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 extremely concise, consisting of two sentences that are front-loaded and waste no words. Every sentence adds meaningful instruction (what it does and how to use it), making it efficient for an agent to parse.

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 the tool's simplicity (one optional parameter, no output schema, no annotations), the description is incomplete. It does not explain what the extracted data contains, any pagination, or error states. An agent cannot determine the return format or handle edge cases without additional context.

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 input schema fully describes the single parameter 'username' (100% coverage), achieving baseline 3. The description adds value by clarifying that providing a username is optional and that the tool can work from the current page, but this context is only marginally beyond the schema's existing description.

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 the verb 'Extract' and the resource 'LinkedIn person profile', making the tool's purpose evident. It implicitly differentiates from sibling tools like linkedin_company and linkedin_feed by specifying 'person profile', but lacks explicit sibling differentiation.

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 provides usage context by mentioning two methods: provide username or navigate first. However, it does not explicitly state when to use this tool over alternatives or exclude scenarios (e.g., 'use linkedin_company for company profiles'), leaving the decision somewhat inferred.

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