get_page_photos

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

With no annotations, the description carries the behavioral disclosure burden. The explicit 'GET' method signals a non-mutating read, and 'type=uploaded' clarifies that only uploaded photos are returned. It does not mention pagination behavior or credential requirements, but these are partly inferable from parameters and the output schema.

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 a single concise sentence with the primary action front-loaded and the endpoint in parentheses. There is no filler, repetition, or unnecessary detail.

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 simple read-only listing tool, the endpoint string and self-explanatory parameter names provide sufficient invocation detail, and the presence of an output schema covers return values. It lacks explicit credential or prerequisite notes, but that is a minor gap for this straightforward GET endpoint.

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 0%, so the description must compensate. It maps page_id to the URL path '{page-id}', but limit and after are left unexplained; their semantics (page size, pagination cursor) are only guessed from their names. This is a clear gap.

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 states a specific verb and resource: 'List photos posted by the Page', and further clarifies via the endpoint 'GET /{page-id}/photos?type=uploaded'. This distinguishes it from sibling tools like get_page_videos or get_page_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 explicit when-to-use or alternative guidance is provided. The resource name 'photos' implies the use case, and 'type=uploaded' narrows scope, but the description does not state when to prefer this over get_page_albums or get_page_videos, nor any exclusions.

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