List post CSV imports

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

No annotations are present, so the description carries the full behavioral burden. It discloses that only the caller's jobs are returned and that counts are included, but it does not describe ordering, read-only status, pagination behavior, or what the counts represent.

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 compact noun phrase with no filler and places the core object ('CSV import jobs') first. It is very efficient, though the efficiency comes at the cost of missing behavioral and pagination detail.

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, no annotations, and no parameter documentation, the description is too thin to fully support correct invocation. It gives a high-level sense of the result but leaves return shape, count semantics, and pagination unspecified.

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%, and the description adds no meaning to 'limit' or 'offset' beyond their names and numeric constraints. With two undocumented parameters, the description should compensate but does not.

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 phrase 'The caller's CSV import jobs with counts' clearly identifies the resource and scope, and the title supplies the list verb. It is not a tautology and is readily distinguishable from create/retry/row-level import tools, though it does not explicitly call out those sibling distinctions.

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?

There is no guidance about when to use this tool instead of get_post_csv_import, get_post_csv_import_rows, or retry_post_csv_import. It neither provides exclusions nor misleading advice, but leaves all tool-selection logic to inference.

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