Get Page Photo Albums

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

Description aligns with readOnlyHint annotation but adds no additional behavioral context such as pagination behavior, rate limits, or auth requirements. Annotations already cover the read-only nature, so description adds minimal value.

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?

Description is short and well-structured, but omits important parameters. It is front-loaded but incomplete, which makes it less effective.

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?

Does not describe pagination ('after' parameter) or output format. Without an output schema, the description should clarify return structure (e.g., list of album objects with IDs). Incomplete for a list operation.

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?

Description only covers page_id and limit, but schema includes four parameters (missing after and response_format). Schema description coverage is low (25%), yet description fails to compensate by explaining pagination or output format meaning.

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?

Title and description clearly state the tool lists photo albums on a Facebook Page. Verb 'Lists' and resource 'photo albums on a Facebook Page' are specific and distinguish it from sibling tools like meta_get_page_photos.

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 explicit guidance on when to use this tool versus alternatives (e.g., meta_get_page_photos for individual photos). No prerequisites mentioned beyond page_id, and pagination via 'after' parameter is omitted.

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