get_page_posts

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

The description discloses the HTTP method (GET), the specific page-scoped resource, and the accepted since/until timestamp formats, which is useful behavioral context. However, no annotations exist, so the description carries the full burden; it does not mention auth requirements, pagination via 'after', rate limits, or what happens with invalid inputs.

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 short, front-loaded with the core purpose, and each sentence earns its place. The timestamp-format note is a valuable addition and the example makes it concrete without adding bloat.

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 tool with 6 parameters, no annotations, and no schema descriptions, this is incomplete. The output schema may explain return values, but an agent still lacks critical invocation details such as how to set page_id, pagination semantics, and field-selection behavior. It is minimally viable at best.

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 for all parameters, but it only explains since and until. It does not explain after as a pagination cursor, limit behavior, the fields selector, or how page_id is used, leaving most parameters underspecified.

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 action and resource: 'List posts published BY a Page', and reinforces it with the exact endpoint GET /{page-id}/posts. The phrase 'published BY a Page' plus the endpoint helps disambiguate this from siblings like get_page_feed and get_page_tagged_posts without needing to open schemas.

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?

There is no explicit guidance on when to use this tool versus alternatives such as get_page_feed or get_page_tagged_posts. The only hint is the phrase 'published BY a Page', which implies a scoped use case, but no exclusions, conditions, or sibling comparisons are provided.

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