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

Annotations already cover the safety profile (readOnlyHint, destructiveHint=false, closed-world), so the bar is low, and the description adds substantive context: the exact contents of the report and how to interpret worst-scoring items diagnostically. It does not cover permissions, rate limits, or cost of the underlying eval runs. No contradiction with annotations.

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?

Front-loaded with the core purpose and payload, and each of the three sentences carries distinct information (what you get, when to call it, how to read the diagnostics). The capitalized 'ACTUALLY' and 'with receipts' are stylistically chatty for a tool definition, but the paragraph stays compact.

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?

There is no output schema, so the description correctly carries the burden of explaining return values, which it does thoroughly for a read-only report. It is a bit light on ordering/recency semantics of 'recent runs' and any notion of time windowing, which the schema does not cover either.

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%, and the description adds no parameter-level detail (no flowId format, no workspace behavior). With the schema fully documenting both params, baseline 3 applies; the description neither compensates nor degrades.

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 resource (a Workbench flow) and enumerates exactly what the tool reports: every targeting eval, recent runs with scores, per-criterion averages, delta vs previous run, and worst items with judge reasoning. That payload enumeration distinguishes it from raw siblings like caliper_evals_runs_list or caliper_evals_get. It lacks an explicit verb and never names a sibling, 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?

Gives a clear trigger: use it BEFORE claiming a flow works or proposing changes, and cite runId + scores. It also prescribes a downstream action for clustered failures (propose a Compass interview for knowledge gaps rather than a prompt fix). No when-not condition or named alternative tool is given, so it stops short of 5.

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