publer_list_posts

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

With no annotations, the description carries full burden for behavioral disclosure. It does not mention pagination behavior, result ordering, rate limits, authentication requirements, or what happens with large datasets. The 'page' parameter is omitted entirely from the description.

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 efficient sentence that covers key filter capabilities. It is appropriately front-loaded. Could be slightly more structured (e.g., listing filters) but remains concise and scannable.

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 7 parameters and no output schema, the description provides adequate initial context but lacks details on pagination, default state, result format, or error scenarios. It is minimally complete for a listing tool but could be more informative.

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% with each parameter documented. The description summarizes filter types (e.g., 'date range', 'post type') but adds no meaning beyond the schema. It omits the 'page' parameter entirely, though the schema covers it. Meets baseline but no extra value.

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 lists and filters social media posts, enumerating relevant filter dimensions (state, date, account, post type, search). This clearly distinguishes it from sibling tools like create, update, delete, and list_media (which handles media, not posts).

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 guidance is provided on when to use this tool versus alternatives. It does not mention when not to use it, prerequisites, or refer to sibling tools like search or analytics. The usage context is implied but not explicitly addressed.

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