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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so safety is covered, and an output schema means return shape need not be described. What the description adds is genuine algorithmic context (mindensity = minimum of the KDE between the two highest peaks, singlet = Huber regression plus prediction band), but it says nothing about what the fitted gates are attached to, whether plotting or compensation alter behaviour, or how the subsample/seed affect determinism.

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 dense sentence with nested parentheticals that front-loads the resource correctly, but the four-way parenthetical enumeration of algorithm internals is expensive to parse and displaces cheaper, more useful content such as when to call it. Nothing is strictly redundant, yet the structure is a method catalogue rather than agent-oriented guidance.

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 30-parameter tool with an output schema and full annotation coverage, the description is adequate on the core gating behaviour but silent on the scale/compensation/plotting/derived-parameter surface and on how the `gating` document relates to the newly fitted gates. An agent can call it with defaults, but not confidently configure it for anything beyond the simplest case.

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%, so the schema already documents all 30 parameters including defaults, ranges and enum meanings, giving a baseline of 3. The description contributes modest extra meaning by explaining what each `cut` value actually computes and that the singlet gate operates on area × height, which ties singlet_area/singlet_height together, but it does not touch scale, compensation, derived parameters or plotting.

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?

Names a specific verb and resource: automated openCyto 2.24 gates fitted on two channels of an FCS file, and enumerates the three gate families it produces (per-axis cut, sequential quadrant, singlet). An agent can tell it is a gating step rather than a QC or clustering step, but the description never contrasts it with near siblings like analyze_flow_cytometry, gate_droplets or cluster_flow_cytometry_flowsom, so differentiation is left to inference.

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 text is entirely 'what it computes' with no 'when to use it': no prerequisites, no mention of required inputs beyond 'an FCS file', and no conditions under which a sibling should be preferred instead. An agent must already know the flow-cytometry pipeline vocabulary to decide to call this rather than analyze_flow_cytometry.

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