facebook_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 describes the basic function without disclosing behavioral traits such as rate limits, authentication needs, or pagination behavior (though end_cursor is in the schema). The description adds minimal value beyond the obvious.

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 a single short sentence, making it concise and front-loaded. However, it could be slightly more structured with bullet points for key details. Overall, it is efficient with no wasted words.

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 3 parameters, no output schema, and no annotations, the description is minimal. It covers the basic purpose but lacks details on return format, error handling, or pagination. For a search tool, this is adequate but could be improved.

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%, so the baseline is 3. The description mentions 'optional location filtering,' which is already clear from the schema (location_uid not required). It does not add significant meaning beyond what the schema already provides.

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 name 'facebook_search_people' clearly indicates the resource. The description specifies 'Search for Facebook people/profiles by keyword with optional location filtering,' which is a specific verb+resource combination that distinguishes it from sibling tools like facebook_search_pages, facebook_search_posts, etc.

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 the tool is for searching people, but it does not explicitly state when to use it versus alternatives. Given the large number of sibling tools (e.g., facebook_search_pages, facebook_search_posts), additional guidance on when to choose this tool would help the agent.

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