facebook_get_page_videos

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

Discloses the per-request limit of 6 and pagination, but lacks information on authentication requirements, rate limits, or behavior when both link and profile_id are provided. With no annotations, more behavioral context would be beneficial.

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 a single, clear sentence with no redundancy. Every word serves a purpose.

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?

For a tool with no output schema, the description omits details on returned video fields (e.g., title, description, metadata) and potential error conditions. It covers the basics but leaves gaps.

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 coverage is 100%, so the schema already describes the parameters. The description adds 'up to 6 per request' which relates to pagination but does not significantly enhance parameter understanding beyond 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 the tool retrieves videos from a Facebook page, specifies a limit of 6 per request, and mentions pagination. This distinguishes it from sibling tools like get_page_posts or get_page_reels.

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?

The description implies pagination for multiple requests but does not explicitly guide when to use link vs profile_id or when to prefer this tool over alternatives like get_page_reels or search_videos.

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