Get 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, and it discloses nothing. It does not mention read-only semantics, authorization needs, error behavior for unknown jobId, or what the returned summary contains.

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 extremely short, but this is under-specification rather than effective conciseness. It is a fragment that saves words by omitting essential information, so the brevity does not add 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?

The tool is simple, but with no output schema and no parameter documentation, the description must explain what a 'summary' includes and how jobId is supplied. 'One import job's summary' provides minimal context but is not enough for an agent to confidently call the tool and interpret its result.

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?

The schema description coverage is 0%, and the one required parameter, jobId, is completely undocumented. The description does not compensate by explaining what jobId represents, where it comes from, or any format expectations.

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 is a noun phrase, 'One import job's summary,' rather than an explicit action statement, so an agent must infer the verb from the tool name. It does identify the resource and the singular scope, which weakly distinguishes it from list_post_csv_imports, but 'summary' is ambiguous and does not make clear what payload will be returned.

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 versus related siblings such as list_post_csv_imports, get_post_csv_import_rows, or retry_post_csv_import. No context, prerequisites, or exclusions are provided.

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