search_people

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

With no annotations, the description must disclose behavior. It notes that results may be fewer than 10 per page due to automatic filtering of hidden profiles. However, it does not mention auth requirements, rate limits, or what happens with empty results, and the wording is confusing.

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 but grammatically poor and awkward (e.g., 'not return all profiles as public'). It lacks clear structure and wastes space on unclear phrasing.

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?

With 9 optional parameters, no output schema, and no annotations, the description should explain pagination, parameter interactions, and result format. It only addresses one minor behavioral nuance and leaves major gaps.

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 coverage is 100%, but the schema descriptions are minimal (e.g., 'Example value: max' for keywords). The tool description adds no additional parameter guidance. For a parameter-heavy tool, this is insufficient.

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 states 'Search profiles by a keyword', which clearly identifies the core function. However, it does not differentiate from sibling tools like 'search_people_by_url' or 'get_public_profile_data', and it omits the return type (list of profiles).

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 on when to use this tool versus alternatives. The description mentions pagination and hidden profiles but does not explain contexts or exclusions (e.g., when to use search_people_by_url instead).

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