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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is fully covered structurally. The description adds nothing behavioral beyond this — no pagination, no result-shape hints, no note on approval-state semantics even though it explicitly names 'approval state' as a return category. It essentially duplicates the readOnly annotation in prose.

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?

A single front-loaded sentence with no filler, so it is not padded. But it is a pure title restatement, so the one sentence does not really earn extra place — it adds no information the title had not already delivered.

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?

There is no output schema, so the description should ideally explain the return shape; it does list the four content categories (runs, plans, approval state, receipts), which partially compensates. Missing are pagination/volume expectations, any filtering behavior, and the fact that it is a multi-entity aggregate read, which matters for an open-world, case-scoped tool.

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?

With 3 required parameters at ~67% schema description coverage, the schema documents company ("Summer company ID") and environment (enum), and the description adds only the scoping concept 'for a case', which maps to the third parameter. It does not explain ID formats or how the three identifiers interact, but the baseline is met since the schema carries most of the burden.

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 verb (Read) and enumerates concrete resources (investigation runs, saved plans, approval state, execution receipts) scoped to a case, so the agent knows what data it retrieves. However, it is a verbatim restatement of the title and offers no differentiation from the sibling summer_investigations_request, which is the write-path counterpart. The purpose is inferable but the line between reading and requesting investigations is left to the agent to guess.

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 statement of prerequisites, and no mention of alternatives such as summer_investigations_request for kicking off a new investigation. The agent must derive the usage boundary purely from the name and the sibling list.

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