search_people

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

No annotations are provided, so the description carries full burden. It mentions that results may have fewer than 10 per page due to hidden profiles being filtered, which adds some behavioral context. However, the explanation is confusing and incomplete, lacking details on filtering logic or other behavioral traits like authentication.

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 short at three sentences. The first sentence is clear, but the latter two are grammatically poor and confusing. It is not optimally front-loaded and could be more concise without the unclear elaboration.

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 9 parameters, no output schema, and no annotations, the description is incomplete. It hints at pagination but does not explain search logic, result format, or how multiple parameters interact. Essential context for effective usage is 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?

Schema description coverage is 100% (all 9 parameters have descriptions). Baseline is 3. The tool description does not add parameter-specific meaning beyond the schema; it only mentions a keyword, ignoring other parameters like firstName, lastName, company. Thus, no extra value.

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 'Search profiles by a keyword', indicating the verb and resource. It distinguishes from sibling tools like 'search_people_by_url' which searches by URL, but does not elaborate on the scope of keyword search.

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?

No explicit guidance on when to use this tool versus alternatives like 'search_people_by_url' or other search tools. The description implies it is for keyword-based profile search but provides no exclusions or context.

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