Create post CSV import

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It specifies input sources and columns but does not disclose whether this creates an import job or posts directly, error handling, permissions, or async processing. For a mutation tool with no annotation safety net, this is a significant gap.

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 two concise sentences with no filler. The primary action and input methods are front-loaded, and the column information is valuable without being verbose. Every phrase earns its place.

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?

With no output schema and no annotations, the description omits critical outcome details. It does not state whether the call returns an import ID, processes asynchronously, or immediately creates posts. Given the sibling tools (list_post_csv_imports, retry_post_csv_import), this ambiguity could lead to incorrect agent behavior.

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%, so the schema already clearly defines the two parameters. The description adds meaningful context by indicating the 'or' relationship between csv and url (implying mutual exclusivity) and by stating the required columns (caption and accountId), which are not present in the schema. This goes beyond what the schema alone provides.

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 the action and resource: 'Bulk-create posts from CSV text or a public CSV URL.' It also names the expected columns. However, it does not explicitly distinguish itself from sibling tools like create_post or schedule_post, so an agent must infer the difference from the word 'bulk' and 'CSV'.

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 usage for bulk creation via CSV, but does not explicitly state when to use it over alternatives such as create_post, nor does it provide exclusions. The context is clear enough to infer a batch scenario, but no direct guidance or alternative routing is given.

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