Search People

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

Annotations provide readOnlyHint=true and openWorldHint=true, which already indicate a safe read operation and potentially incomplete results. The description adds no additional behavioral context such as pagination, rate limits, or authentication requirements. It does not contradict the annotations, and the simple statement is consistent with the expected behavior.

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: 'Search for people on LinkedIn.' It is front-loaded with the verb and resource, contains no unnecessary words, and perfectly communicates the tool's core purpose.

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?

The tool includes a comprehensive input schema with parameter descriptions and an output schema, so the description does not need to explain return values or parameter syntax. The description is complete for a fully specified search tool, and the annotations cover safety and open-world semantics.

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 description coverage is 100%, and each parameter has a detailed description in the input schema. The tool description adds no parameter-specific meaning, so it neither enhances nor detracts from the schema. Given the high coverage, a score 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 function: 'Search for people on LinkedIn.' It uses a specific verb ('search') and resource ('people'), and distinguishes from sibling tools like search_companies and search_jobs by indicating the entity type.

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 any exclusions or alternative tools, leaving the agent to infer from the tool name and sibling list. The only alternative reference is in the current_company parameter description, but not in the main description.

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