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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered and the description does not contradict it. The description usefully adds the binning model (equal time bins over the population's time span) and what is reported per time range, but omits failure conditions — e.g. what happens with no time parameter, a missing compensation matrix in 'file' mode, or an unreadable gating document.

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?

It is front-loaded with the core definition and contains no filler, but it is delivered as one long run-on sentence with semicolon-chained clauses and a trailing 'dt' that is unexplained. Splitting it into purpose / per-bin output / per-range output would make it markedly easier to scan.

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?

For a 31-parameter tool with nested objects and an output schema, the description covers the analytical concept and return shape at a high level, so the biggest gaps (return values, field names) are handled elsewhere. It says nothing about how the target file is located via document/_files/_subject or about the interaction between gating, population and plot_population, which is where a caller is most likely to go wrong.

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% across all 31 parameters, so the schema already carries the per-parameter meaning (scale, threshold, smoothing, half_width, compensation, etc.), and the baseline of 3 applies. The description reinforces the conceptual chain (threshold → optional above_threshold_only → smoothing → per-bin statistic) but adds no syntax or edge-case detail beyond what the schema states.

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 concrete computation — a statistic of one channel of an FCS file over acquisition time — and enumerates exactly which statistics (median, mean, geomean, percentile, % above threshold) and derived kinetics (peak, slope, AUC, dt). It implicitly separates it from the broader flow-cytometry siblings by insisting on the time axis, but it never names analyze_flow_cytometry or compare_flow_cytometry_populations as the non-kinetic alternatives.

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 explicit when-to-use or when-not-to-use instruction. The phrase 'over acquisition time (FlowJo's Kinetics)' hints that this is for time-resolved data, but an agent is left to infer that a static population summary should instead go to a sibling tool, and nothing calls out a prerequisite such as the file needing a time channel.

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