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

The annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is clear. The description adds that the tool computes cell subpopulation phenotypes and proportions, which is useful output behavior beyond the annotations, though calculation gating rules are not described.

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 pipe-delimited structure is front-loaded and compact, with purpose, usage, aliases, and return value easy to scan. There is some redundancy from bilingual duplication and keyword-style aliases, but nothing materially wasteful.

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 simple four-parameter phenotyping computation with full schema coverage and clear annotations, the description supplies enough context to invoke it and states what is returned even though no output schema exists. Only the handling of optional markers and phenotype-gating logic is left implicit.

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 four marker parameters are already documented in the schema. The description mentions markers generally but adds no syntax, thresholds, optional-marker behavior, or other meaning beyond what the schema provides, so the baseline of 3 applies.

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 states a specific action, 'assign cell phenotypes and proportions from multiplex immunofluorescence markers,' and identifies the resource as mIF phenotyping. An agent can understand exactly what the tool computes without opening the schema.

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 'USE WHEN' clause gives a clear triggering context: assigning phenotypes and proportions from multiplex immunofluorescence markers. It does not provide when-not conditions or alternative sibling tools, but no closely related sibling is present in the supplied list.

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