Get post CSV import

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

Annotations already declare readOnlyHint=true, openWorldHint=true, and destructiveHint=false, so the safety profile is fully covered elsewhere. The only added behavioral signal is the word 'summary', which weakly suggests an aggregated view rather than raw rows, but it discloses nothing about error behavior for missing/expired jobs or what fields come back.

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?

It is only a sentence fragment, so there is no waste, but this is under-specification rather than conciseness. There is no front-loaded verb or scope statement, and the single noun phrase carries almost no information.

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 read-only single-record fetch this should be easy to complete: identify the ID's origin, contrast with the rows and list siblings, and note whether a missing job errors or returns empty. None of that is present, and with no output schema the description is the only source for what comes back.

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 bears full responsibility for explaining jobId - its format, where to obtain it, and whether it is the import ID or something else. It says nothing, leaving the sole required parameter unexplained in both the schema and the prose.

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 name plus 'One import job's summary' conveys that this retrieves a single CSV import job record rather than a list, which loosely separates it from list_post_csv_imports. But 'summary' is ambiguous - it could mean aggregate counts, status metadata, or a truncated row set - and the description never states what is actually being fetched. An agent can guess the resource but not the content.

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?

No guidance on when to call this instead of list_post_csv_imports or get_post_csv_import_rows, and no mention that a valid jobId from the list endpoint is a prerequisite. The word 'One' hints at a single-record lookup but the choice among the three sibling import tools is left entirely to inference.

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