nv_search_people

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

No annotations are provided, so the description carries the full burden. It only states the tool allows searching with filters, omitting behavioral traits like read-only nature, authentication requirements, rate limits, or return format. The description adds minimal transparent context beyond the name.

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 very concise (one sentence plus action reference) but lacks detail. It is front-loaded but insufficiently informative for a tool with a nested filter object. Could be improved with brief usage guidance.

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 complexity (3 parameters, nested filter with multiple fields) and no output schema, the description is incomplete. It does not mention pagination, response format, or any limitations. The schema provides parameter details but behavioral and output context are missing.

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?

All parameters (term, limit, filter) are fully described in the input schema (100% coverage). The description adds no additional meaning, such as clarifying the term as keyword search or the AND logic for filters, which is already in the schema. Baseline 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 specifies the verb 'search' and resource 'people in Sales Navigator', distinguishing it from sibling tools like nv_search_companies and the non-nv search_people. The action reference (nv.searchPeople) reinforces the scope.

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 implies it is for Sales Navigator people searches but does not explicitly state when to use this over alternatives like search_people or nv_search_companies. No when-not-to guidance is provided.

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