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

Annotations already declare readOnlyHint=true, openWorldHint=false and destructiveHint=false, so the safety profile is covered. The description adds that the read surfaces per-row search status and the resulting list, which hints at scope, but says nothing about batch lifecycle state, auth/permissions, or pagination for large runs.

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?

One short sentence, verb-first, with no filler or repetition of the title. It is efficient, though the terseness is part of why the definition under-specifies the tool.

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, the description does at least sketch the return shape (rows, search status, resulting list), which is worth something. But for a tool sitting in a prepare/approve/cancel batch lifecycle with an undocumented required id, an agent is left guessing about both input provenance and lifecycle preconditions.

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% for the single required parameter batch_id, and the description never mentions it — no indication of where the id comes from (presumably prepare_investigation_batch) or what happens with an unknown id. With the schema providing only a type and minLength, the description fails to compensate.

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 names a verb ("Reads") and describes the payload ("each input row, its search status and the list it led to"), but never identifies the resource as an investigation batch addressed by an id. Against siblings like get_investigation_results, get_investigation_inputs, and prepare_investigation_batch, an agent cannot tell from the text alone what distinguishes this read.

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 when-to-use guidance, no prerequisites (e.g. whether the batch must first be prepared or approved), and no mention of any alternative tool. The sibling list contains at least three closely related investigation tools, so the absence of routing guidance is a real gap.

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