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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds genuine context by describing the return contents (summary, ranked items, per-item evidence), which is real value beyond the annotations, but omits freshness/pagination or whether it errors when no result exists.

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 tight sentence with no filler, front-loaded with the resource and payload shape. It is a noun fragment rather than a full statement of action, which slightly weakens it, but nothing is wasted.

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 cover the return shape, which is the main thing an agent needs. However, for a getter tied into a run_insight/list_insights workflow, it lacks the id semantics and any error/empty-state behavior, so it is only adequate.

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 single required 'id' parameter is never mentioned in the description. The agent gets no hint whether 'id' refers to the insight id from list_insights, a run id, or accepts both integer and string forms as the schema allows. With 1 parameter and zero coverage, this gap matters.

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 specific resource ('the latest result of an insight') and the shape of the payload (summary, ranked items, evidence). It distinguishes itself implicitly from list_insights and run_insight, but the verb is only implied and no sibling is named explicitly.

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 when-to-use guidance, no prerequisites, and no alternatives named. With siblings run_insight and list_insights present, the agent must infer that this is the retrieval step following generation. Nothing tells it when this tool is or isn't appropriate.

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