Create post CSV import

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

The annotations already declare readOnlyHint=false, openWorldHint=true, and destructiveHint=false, so the safety profile is covered. The description adds that this is a bulk CSV import and notes expected columns, but it does not explain import-job behavior, validation, partial failures, or what is returned.

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?

Two short sentences, front-loaded with the core action and source options. There is no wasted language and the extra column note is directly relevant.

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?

This is a mutating bulk-import tool with no output schema and an open-world hint. The description covers the basic action but omits important context such as whether the import is asynchronous, how import progress is tracked, and what happens with invalid rows.

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 two parameters are already documented. The description adds useful semantics beyond the schema by naming the expected CSV columns, caption and accountId, although it does not explicitly clarify whether exactly one of csv or url must be supplied.

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 states a specific verb and resource: "Bulk-create posts" from CSV text or a public CSV URL. The word "Bulk" and the CSV source distinguish it from the single-post create_post sibling without needing to name it.

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 implies usage for bulk post creation and names two input sources, but it does not explicitly say when to use this instead of create_post, nor does it state prerequisites or when not to use it. Usage is inferable but not fully guided.

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