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

Annotations already declare readOnlyHint=true and destructiveHint=false, and openWorldHint=false, so safety is covered. The description adds one genuinely useful behavioral fact beyond annotations — that the response carries the activePublication CAS target needed for an external generation write — but omits auth/superadmin scoping behavior and any pagination or size characteristics.

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 that wastes no words and leads with the core action. It is arguably too compressed for the payload it promises, but every clause earns its place.

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?

No output schema exists, yet the description compensates by naming the return contents (metrics, findings, terminal status, CAS target). With annotations covering the safety profile and the schema covering all parameters, the definition is close to complete; only the sibling-routing and auth context are missing.

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 (sessionId, customerId, conversationId) are already fully documented in the schema, including the sessionId-vs-conversationId precedence rule. The description adds nothing about parameter usage, so the baseline 3 applies.

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?

States a specific verb and resource ('Get detailed insights for a specific run') and enumerates the payload (metrics, findings, terminal status, CAS target). It is clear what it does, but it never distinguishes itself from close siblings like get_insights, get_run, or get_run_finding_context, so an agent must infer the boundary.

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, and no routing to alternatives among the many get_* siblings. The mention that the CAS target is 'required for an external generation write' implies a downstream step but never names publish_external_run_insight_generation or says when to call this tool instead of get_run.

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