get_v1_fbsearch_places

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

No annotations are provided, so the description carries full burden. It merely says 'Search locations' without disclosing behavioral traits such as auth requirements, rate limits, expected response format, or any side effects.

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?

Extremely brief but under-specified. The single sentence repeats the path and title with minimal added value. Essential information is missing.

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 3 parameters, no output schema, and no annotations, the description is completely inadequate. It does not explain the response format, pagination, or any constraints on the search.

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% description coverage and the tool description adds no explanation beyond parameter names. The query parameter is required but its meaning is only implied by 'Search locations'; lat and lng defaults are given but no guidance on how to use them.

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?

Description states 'Search locations' which is somewhat clear but vague. It does not specify what kind of locations (e.g., places, businesses) and fails to distinguish from similar sibling tools like get_v1_fbsearch_topsearch or get_v1_location_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 guidance on when to use this tool vs alternatives. There are many search-related siblings (e.g., get_v1_fbsearch_topsearch, get_v1_fbsearch_topsearch_hashtags, get_v1_location_search) with no comparative context provided.

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