get_v2_fbsearch_reels

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

No annotations are provided, and the description does not disclose any behavioral traits such as pagination (implied by reels_max_id), authentication needs, rate limits, or return format. The description is too brief to provide meaningful behavioral context.

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 short (two lines), but it lacks structure and substance. The HTTP path is included but not essential, and the single sentence fails to provide enough information. Under-specification is not conciseness.

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 complexity of 3 parameters, many sibling search tools, and no annotations or output schema, the description is severely incomplete. It does not cover return values, pagination, or how to use optional parameters, making it inadequate for agent selection.

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%, meaning the input schema provides no descriptions for parameters. The description does not add any information about 'query', 'reels_max_id', or 'rank_token' beyond their names. The tool's purpose is implied but no parameter semantics are explained.

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 top content by keyword', which combined with the tool name 'get_v2_fbsearch_reels' clearly indicates it searches for reels using a keyword. However, it does not explicitly distinguish this from sibling search tools like get_v2_fbsearch_topsearch or get_v2_fbsearch_accounts.

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 compared to other search tools. There is no mention of prerequisites, exclusions, or alternative tools.

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