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

Annotations already cover the safety profile (readOnlyHint true, destructiveHint false), and the description goes well beyond them: the rounded nature of view_count (27K becomes 27000), which engagement fields are absent, the never-false nullable is_paid_partnership semantics, and pagination coupling. The cost disclosure is the weak point, since the pasted pricing block says both "at least 10 Nexscope credits" and "1 credit per request," which is contradictory and could mislead a cost-sensitive agent.

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?

It is front-loaded correctly, with the fetch statement and field list first and caveats after. However, the entire description is duplicated verbatim and a pasted marketing/pricing block ("Facebook Profile Reels API View Pricing ... 1 credit per request") is spliced into the middle, so roughly half the text is redundant and the cost messaging conflicts.

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?

There is no output schema, so the description carries the full burden of describing the return shape, and it does so with an explicit field list plus exclusions and value semantics. Pagination, the detail-endpoint escape hatch, and nullable-field behavior are all covered, leaving nothing essential an agent needs before calling it.

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 each of the three parameters is already documented, giving the baseline of 3. The description does add one genuinely new constraint the schema lacks: next_page_id and cursor must be passed together from the previous response, since the schema describes each identically as "to paginate through to the next page." That is a modest but real increment.

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 opening sentence states a specific verb, resource, and scope: "Fetches up to 10 reels per request from a public Facebook page," and the field list leaves no doubt about what comes back. It also separates the tool from the per-post detail path (/v1/facebook/post). The one ambiguity is the name/title saying "Profile Reels" while the description and schema only speak of a "public Facebook page," so an agent cannot tell whether a personal profile URL is acceptable.

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?

It states when to use this list endpoint and when to switch: call /v1/facebook/post per reel when engagement metrics or a precise view_count are needed, and it explicitly says there is no batch detail parameter here. It also gives a negative usage rule (do not infer pinning from ordering) and the prerequisite for pagination (both next_page_id and cursor from the previous response).

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