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

The readOnlyHint annotation already establishes that this is a safe read operation, and the description is consistent with that. The description adds detail about the returned analytics categories but does not provide additional behavioral context such as response format, pagination, or permission requirements. With the safety profile covered by annotations, this is adequate but not rich.

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?

The description is one sentence with the main action front-loaded and the output components contained in a parenthetical list. Every phrase carries information and there is no filler or duplicated schema content.

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?

The tool is simple: one required parameter, a read-only annotation, and a description of the returned analytics categories. Since there is no output schema, the description covers the response at a useful level of detail. It could be more complete by noting how this report differs from sibling tools, but nothing essential is missing for invoking it.

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 0% schema description coverage, the description shoulders the burden of interpreting the single utId parameter. Calling the target 'a UT' makes clear that utId is the UT identifier. It does not specify format or retrieval source, but for a single, self-explanatory parameter this is sufficient guidance.

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 action and resource ('Returns the quantitative analytics for a UT') and enumerates the main content categories (counts, success distribution, duration stats, variant info), so its purpose is clear. It does not explicitly distinguish itself from siblings like get_ut, get_transcript, or compare_rounds, though the quantitative angle makes it distinguishable.

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?

The intended use is implied: call this when you need quantitative analytics for a UT. There is no explicit when-to-use/when-not-to-use guidance or reference to alternative sibling tools, so the agent must infer selection criteria from the tool name and purpose.

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