get_v2_fbsearch_reels

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds value beyond that: it discloses that this is a live Instagram request billed per call, and that pagination relies on reels_max_id and rank_token from the previous response.

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?

Three sentences, zero padding. Purpose is front-loaded, the alternative follows, and pagination/cost details are packed at the end. Every clause carries distinct 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?

No output schema exists, but the description covers selection, cost model, and pagination mechanics, which is most of what an agent needs. It does not hint at the response shape, though the pagination note indirectly signals the return fields an agent will reuse.

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 only 25% (safe_int only), so the description must compensate. It explains the origin and use of rank_token and reels_max_id as pagination cursors from the prior response, which the schema does not say. It leaves query semantics and the safe_int flag to 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?

States a specific verb and resource (search reels by keyword) and immediately distinguishes it from the nearest sibling by naming get_v1_hashtag_medias_clips_chunk as the hashtag-scoped alternative. An agent can route between the two without opening either schema.

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?

Explicit when-to-use ('find short videos about a topic') plus an explicit when-not/alternative ('use get_v1_hashtag_medias_clips_chunk for reels under one specific hashtag'). Nothing about selection is left to inference.

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