fb_list_posts

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

With no annotations, the description carries the full burden of behavioral disclosure. It only says 'List recent posts' and adds no detail about pagination, return format, ordering guarantees, or whether unpublished/scheduled posts are included. The behavior is not misleading, but it is minimally disclosed beyond the tool's name.

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 one concise sentence with no filler. It front-loads the key facts: the operation, the resource, and the scope.

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 optional-limit list operation, the description is mostly adequate, but with no output schema it does not explain the return shape or pagination behavior. Adding a note about what the returned post objects contain or how 'recent' is determined would make it complete.

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%, and the description does not mention the only parameter, `limit`. The schema's default/min/max constraints and the parameter name provide enough to invoke the tool, but the description itself adds no semantic value for the parameter.

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 clearly states a specific verb ('List'), resource ('posts'), and scope ('from the Facebook Page'). It distinguishes this tool from siblings like fb_get_post (single post) and creation/deletion tools, so an agent can tell it apart.

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 implies this is for listing recent page posts, but it does not explicitly state when to use it versus fb_get_post or the creation tools. The usage context is inferable from the description and sibling names, but no explicit when-not or alternatives are given.

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