get_v1_fbsearch_topsearch

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

No annotations provided, and the description does not disclose behavioral traits such as read-only nature, authentication requirements, rate limits, or pagination. The tool likely performs a read operation but this is not stated.

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 concise but under-specified—repeating the name without substantive information. True conciseness should preserve clarity, which is absent here.

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 abundance of sibling tools and lack of output schema, the description is critically incomplete. It does not explain what 'topsearch' returns, how results are structured, or how it differs from other search endpoints.

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 single parameter 'query' lacks description in both schema (0% coverage) and tool description. The description adds no meaning about the query format, expected input, or its role in the search.

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 merely repeats the tool name 'Fbsearch Topsearch' without specifying what it returns (e.g., top users, places, or combined results). It fails to differentiate from siblings like get_v1_search_users or get_v1_fbsearch_places.

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 the many sibling search tools (e.g., get_v1_search_hashtags, get_v2_fbsearch_topsearch). The description lacks any context for appropriate use.

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