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

Annotations already declare readOnlyHint=true, openWorldHint=true and destructiveHint=false, so the safety profile is fully covered by structured fields. The description adds nothing beyond that — no note on pagination behavior, rate limits, or whether the page must be public, despite an end_cursor parameter implying paginated results.

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?

A single efficient sentence that front-loads the resource and scope with no filler. It is arguably too terse to be maximally useful, but there is no wasted wording.

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?

An output schema exists, so return values need not be described, and the two parameters are schema-documented. Still, for a paginated open-world fetch tool the description omits contract details (pagination loop, page visibility requirements) that would help an agent call it correctly.

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 100%, so 'link' and 'end_cursor' are already documented in the schema; baseline is 3. The description adds no syntax, format, or pagination semantics beyond what the schema provides.

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 ('Get') and resource ('reels/short videos from a Facebook page'), which clearly separates it from facebook_get_page_posts and facebook_get_page_videos. It does not, however, explicitly explain how it differs from the closely-named facebook_get_page_videos sibling, leaving the distinction to be inferred.

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 gives no when-to-use guidance, no prerequisites, and never mentions an alternative tool. An agent must guess whether reels should be fetched via this tool or the nearby get_page_videos sibling.

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