List social posts

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

Beyond the readOnlyHint and openWorldHint annotations, the description adds meaningful behavioral detail: per-platform unit costs, the fact that failed calls are not billed, and exact cursor-based pagination behavior. These are operational traits an agent could not infer from the annotations alone.

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 dense but well structured: it front-loads the purpose and source-selection rule, then provides a compact platform matrix, followed by pagination and cost notes. Every section contributes directly to correct invocation.

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 complex, nested, multi-platform list tool, the description covers platform selection, allowed params per platform, pagination, and billing. It does not describe the shape of returned posts, and there is no output schema, so return-value expectations remain somewhat underspecified.

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?

The input schema only exposes platform plus a free-form params object, so the description carries almost all parameter semantics. It enumerates which params each platform accepts, including required-parameter notation and platform-specific options such as userId, sound, playlist, relatedTo, sort, and period.

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 and resource: listing posts from a social platform. It also distinguishes the tool's breadth from single-post siblings by explaining that params select among account, search, hashtag, community, sound, company, playlist, related-post, or trending-feed modes.

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?

It gives strong guidance on how to choose a source via params and explicitly covers pagination by saying to call again with only the previous cursor. It does not explicitly compare against siblings such as get_social_post or get_social_profile, so it stops short of full when/when-not/alternatives guidance.

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