get_v2_fbsearch_topsearch

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

No annotations are provided, so the description must carry full behavioral disclosure. It mentions 'GET' but does not describe authorization needs, rate limits, pagination behavior (despite next_max_id parameter), or what 'top' means.

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 short but includes an unnecessary HTTP method prefix ('[GET /v2/fbsearch/topsearch]') which could be omitted. It is concise but could be more informative without additional length.

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 no output schema, no annotations, and a poorly documented parameter (next_max_id), the description lacks completeness. For a search tool with many siblings, it should explain the result type and pagination.

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 0%, so the description should compensate. It hints that 'query' is for keyword search but provides no detail about 'next_max_id' (e.g., pagination token). It adds marginal value over the schema.

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 clearly states 'Search top content by keyword', which indicates a search tool for top content. However, it does not differentiate from siblings like get_v2_fbsearch_accounts or get_v2_fbsearch_reels, which also search but for specific types.

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 alternatives. With many sibling search tools (e.g., get_v1_fbsearch_topsearch, get_v2_search_hashtags), the description offers no context for selection.

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