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

Annotations already establish this as a pure read (readOnlyHint=true, destructiveHint=false), so the safety profile is covered. The description does add genuine context beyond annotations by disclosing that the payload carries a terminal status and the activePublication CAS target needed for an external generation write, tying it to publish_external_run_insight_generation. It still says nothing about pagination, cost, or result size.

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 tight sentence with the resource and the full content list front-loaded; no filler. The trailing "activePublication CAS target required for an external generation write" is dense internal jargon, which slightly reduces first-pass readability.

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 tool with 3 fully documented parameters and no output schema, the description covers what comes back and why one field matters downstream. The remaining gap is selection guidance against neighboring insight/get tools, none of which the description addresses.

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 100%, so all three parameters are already documented in the schema, making the 3 baseline appropriate. The description adds no format or syntax detail for sessionId, customerId, or conversationId, though it does clarify that these resolve to "a specific run."

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 verb+resource ("Get detailed insights for a specific run") and enumerates what those insights contain (metrics, findings, terminal status, CAS target), which separates it from get_run, get_insights, and get_run_finding_context. It stops short of explicitly naming a sibling it is not, so it lands at 4 rather than 5.

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 statement of when to choose this tool over get_run, get_insights, get_run_finding_context, or regenerate_run_insights, and no prerequisites or exclusions are given. The only routing hint ("sessionId used only when conversationId is not provided") lives in the schema, not the description.

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