search_people_by_url

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

Discloses that some profiles are hidden and automatically filtered, causing fewer results. However, no annotations provided, and description does not cover other behavioral aspects like data freshness or authorization.

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?

Description is too brief but poorly worded with grammatical errors ('This is because not return all profiles as public'). Lacks clarity and structure.

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?

No output schema, no annotations, and no explanation of URL-related functionality. Does not specify what 'keyword' refers to or how filtering works. Incomplete for a tool with no parameters.

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?

Input schema has 0 parameters, but description mentions 'by a keyword' implying a parameter. This is misleading. Baseline for 0 params is 4, but contradiction reduces score.

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?

Describes searching profiles by keyword, but tool name 'search_people_by_url' suggests URL-based search. Contradiction between name and description. Does not differentiate from sibling 'search_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 explicit guidance on when to use this tool vs alternatives like 'search_people' or 'get_public_profile_data_by_url'. Only mentions pagination issue without context.

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