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

Annotations already declare a safe read-only, non-destructive operation, so the bar is lower. The description adds useful context that the response covers result/confidence/stop status and that daily/hourly series and activity are optional, but it omits pagination, permissions, or other operational behavior.

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 a single efficient fragment with no wasted words, and the returned information is front-loaded. However, for a 10-parameter query tool it is too terse to be appropriately sized, bordering on under-specification rather than useful conciseness.

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 and 0% schema description coverage, the description carries the full burden of explaining a complex 10-parameter query. It only broadly indicates returned data and optional series/activity, leaving required workspace semantics, date filtering, detail levels, and metric selection unexplained.

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% across 10 parameters, so the description must compensate and largely does not. It only hints at the series enum and include_activity boolean, while test, group, since, until, detail, metric, event_name, and workspace remain unexplained beyond their names.

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 fragment identifies a specific resource and the information returned: experiment results, confidence, and stop status, plus optional daily/hourly series and activity. It is clear enough for an agent to understand the tool's purpose, though it lacks an explicit verb and does not differentiate from siblings like abtests_list.

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 description gives no guidance on when to use this tool versus abtests_list, abtests_prepare, or other A/B test siblings. It also provides no prerequisites, exclusions, or scenario-based cues for selecting this retrieval tool.

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