List Albums

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

Annotations already declare readOnly, idempotent, non-destructive and open-world, so safety is covered. The description adds value beyond that by disclosing the page-at-a-time pagination model and the full set of returned fields, which is the main behavioral unknown for a list tool. It does not mention permissions on the Page or rate limits, keeping it just below 5.

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?

Two sentences, front-loaded with the verb and resource. The field enumeration is long but each field listed is information an agent would otherwise have to guess (no output schema). Slight density cost but no wasted framing.

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?

With no output schema, the description carries the return-shape burden and does so well by naming the fields including the `id` needed downstream. Pagination and cursor expiry are handled in the schema. Missing are ordering guarantees and any Page-level permission note, minor for a read-only list.

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% and each of `after`, `limit` and `profile` is fully documented in the schema, including cursor expiry and defaults. The description adds no parameter-level detail beyond the schema, so the baseline 3 applies.

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 ('List a Page's photo albums') with the pagination scope ('one cursor page at a time') and enumerates exactly what is returned. It also names the sibling it feeds into, so an agent can distinguish it from facebook_list_photos and facebook_list_pages.

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?

Clear usage context: call it to enumerate albums, then pass the returned `id` as `album_id` to facebook_list_photos. That chaining guidance is explicit. It lacks an explicit 'do not use when…' exclusion (e.g. use facebook_list_photos to go straight to photos), so it stops short of the top mark.

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