people_search

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

No annotations are provided, so the description bears full responsibility for behavioral disclosure. However, it only states 'find people' without mentioning read-only nature, rate limits, authentication needs, or any side effects. The external link does not compensate for the lack of inline transparency.

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 short—one sentence and a URL. While concise, it under-specifies the tool's functionality for a complex parameter set. The sentence is front-loaded, but it does not earn its place as it lacks detail; an external link is not a substitute for inline explanation.

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 (many parameters, no annotations, no output schema), the description is severely incomplete. It does not explain return values, pagination, or any behavioral context. The external documentation link is not part of the description text.

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 description adds no parameter information beyond what is already in the input schema. The top-level 'query' parameter has no description, and the sub-properties are well documented in the schema, but the description does not explain how to construct the query object or provide examples. With 0% schema description coverage, the description fails to compensate.

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 'find' and resource 'people', making the basic purpose obvious. It distinguishes from sibling tools like organization_search (which searches organizations) and people_enrichment (which enriches specific people).

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 guidance is provided on when to use this tool versus alternatives such as people_enrichment or organization_search. There is no mention of prerequisites or context, leaving the agent to infer usage solely from the tool name and siblings.

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