Fetch Meta Ads Pagination URL

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

Annotations already convey read-only, idempotent, and safe behavior. The description adds valuable context beyond annotations: the URL already contains the access token, and warns not to modify it. It also states the return format matches the original response.

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 highly concise and well-structured: a one-line summary, usage guideline, args/returns sections, examples, and a warning note. Every sentence adds value with no redundancy.

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?

Given the tool's simplicity (1 param, no output schema), the description is complete: it explains the input, output (same format as original), and provides multiple usage examples and a critical security note.

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% for the single parameter, providing baseline 3. The description adds meaningful context: the URL includes the access token and all necessary parameters, and explicitly advises not to add or modify the token, which is critical for safe usage.

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 explicitly states the tool fetches the next or previous page from a Meta Graph API pagination URL, clearly distinguishing it from sibling tools that perform different operations (e.g., getting entities or insights).

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 provides explicit when-to-use guidance ('Use this tool whenever...') and concrete examples for specific preceding calls. It lacks an explicit when-not-to-use statement, but the sibling context makes it clear this is the only pagination tool.

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