find_linkedin_profile

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

No annotations are provided, so the description carries full burden. It does not disclose behavior like authentication needs, rate limits, or what exactly is returned (e.g., profile slug, URL, or full profile data). The schema mentions returning a 'profile slug,' but the tool description omits this, leaving the agent uncertain about the output.

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 sentence of 13 words, instantly conveying purpose. It is front-loaded with the action verb 'Find' and the resource, with no extraneous information.

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 one-parameter tool, the description is minimally complete. However, it lacks details about the output format or error handling. Without an output schema, the agent cannot fully anticipate the tool's response, making the description somewhat incomplete.

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 only parameter 'query' has a description in the schema that explains it finds the LinkedIn profile slug. The tool description adds no additional meaning beyond what the schema provides. With 100% schema coverage, a baseline of 3 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 states the tool's action: 'Find someone's LinkedIn profile from a query of their name or other details.' It specifies the verb 'find' and the resource 'LinkedIn profile,' and differentiates from sibling tools like 'get_linkedin_profile' (which likely works with an existing identifier) and 'search_linkedin_people' (which searches with specific criteria).

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 no guidance on when to use this tool versus alternatives. It does not mention when not to use it, prerequisites, or mention sibling tools. An agent would need to infer usage based on the name alone.

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