performance_analyze_insight

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

Annotations already declare readOnlyHint=true, so the safety profile is covered. The description adds useful context that this read concerns insights highlighted from a trace recording, but doesn't say what the returned 'more detailed information' contains or how the insight is selected.

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. Every phrase contributes: operation, resource, and source context.

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 readOnlyHint, a complete schema, and a clear purpose, the description is mostly sufficient. The main gap is not describing output shape, and it relies on the trace context to imply the prerequisite workflow.

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?

The schema has 100% parameter descriptions, so the baseline applies. The description broadly reinforces the insight-set context but doesn't add detail beyond the schema's pageId/insightName/insightSetId explanations.

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 uses a specific verb ('Provides more detailed information') and identifies the resource ('specific Performance Insight' within an insight set from trace recording). It clearly states what the tool does, though it doesn't contrast with sibling performance tools.

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?

It implies the tool is used after a trace recording has produced highlighted insights, and the insightSetId parameter instructs to use IDs from the 'Available insight sets' list. No explicit when-to-use/when-not-to-use guidance or alternatives are given.

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