Get Page Videos

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

Annotations already indicate readOnlyHint=true and destructiveHint=false, so the agent knows it's safe. The description adds minimal behavioral context beyond stating it lists videos. No disclosure of pagination behavior or other traits.

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 concise with one sentence and a brief parameter list. It is front-loaded with the main action, but could be more structured by including all parameters, especially 'after' for pagination.

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 list tool with four parameters and no output schema, the description lacks explanation of pagination ('after') and output format ('response_format'). Given the number of sibling tools, more context about how this fits in would be helpful.

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 25% (only response_format has description). The tool description explains page_id and limit but omits 'after' (pagination cursor) and 'response_format'. While it adds some value, it does not fully compensate for the low schema coverage.

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 lists videos uploaded to a Facebook Page, using a specific verb and resource. It distinguishes from sibling tools like meta_get_page_photos (photos) and meta_get_page_albums (albums).

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 such as meta_get_live_videos or meta_create_video_post. The description lacks context about when not to use or how it differs from similar tools.

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