get_v3_fbsearch_places

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

No annotations are provided, and the description omits any behavioral traits. It does not disclose return format, pagination, authentication requirements, or limitations. The burden falls entirely on the description, which fails to provide necessary context for safe invocation.

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 brief (2 lines) but at the cost of completeness. It repeats the HTTP method and endpoint already in the name and adds little value. The structure is minimal and lacks front-loading of key information.

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 absence of an output schema and only one parameter, the description should explain the response or behavior but does not. It is completely inadequate for a search tool, providing no context about what data is returned or how the tool behaves.

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 only parameter is 'query' (string, required). Schema description coverage is 0%, meaning the description does not explain the parameter. The keyword 'Search' implies the query is a search term, but no details on format or examples are given, failing to compensate for the low schema coverage.

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 places', which clearly indicates the tool searches for places using a query. However, it lacks specificity and does not differentiate from sibling tools like get_v1_fbsearch_places or get_v2_fbsearch_places, which have similar purposes.

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. There are multiple fbsearch_places tools, but the description does not explain differences or provide context for selecting this version.

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