list_organic_posts

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

With no annotations, the description must disclose behavioral traits. It only states basic listing and filtering, but omits details like ordering, pagination (limit parameter not addressed), authentication requirements, or rate limits. The lack of transparency limits an agent's ability to anticipate behavior.

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, front-loaded with the action and resource. No wasted words; every element (platforms, filtering) adds value.

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 (3 parameters, no output schema, no annotations), the description is moderately complete. It covers the core action and main filters but misses the limit parameter and return format. For a listing tool, more detail on pagination would improve completeness.

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. It mentions brand_id and platform as filters, adding meaning beyond the schema. However, the limit parameter is not explained. The description partially covers parameters but is incomplete.

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 verb 'List' and the resources 'Instagram + TikTok organic posts'. It also specifies filtering options, differentiating it from siblings like 'get_organic_post' (single post) and 'list_brands' (brands). The purpose is unambiguous.

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 clear context on when to use the tool: to list organic posts filtered by brand_id and/or platform. However, it does not explicitly exclude cases or mention alternatives, such as using 'get_organic_post' for a single post. The guidance is good but not exhaustive.

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