assess_parallelism

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

With no annotations, the description carries full responsibility for disclosing behavior. While it names the statistical tests, it fails to describe output format, assumptions, or whether it returns a decision/p-value. It does not mention any side effects, auth needs, or data constraints, making behavioral expectations unclear.

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, well-structured sentence with no redundant words. It conveys the essential method succinctly, making it easy for an agent to parse.

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?

Given the tool's complexity (statistical testing) and the absence of output schema and annotations, the description is incomplete. It does not describe what the tool returns (e.g., a statistic, p-value, or decision), nor does it mention required input assumptions or edge cases. Without this, an agent cannot fully predict the tool's behavior after invocation.

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%, and the description adds no meaning to the parameters. It does not explain what 'reference_responses' and 'test_responses' represent or how they relate to the slope/asymptote analysis. The parameter names are somewhat self-explanatory, but the description fails to compensate for the lack of schema documentation.

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 clearly states the tool's function with a specific verb ('Computes') and identifiable resource ('shared slope and asymptotes consistency'), specifying the statistical methods (F-Test and TOST). This distinguishes it from sibling tools like calculate_4pl_curve or calculate_z_factor, which address different aspects of assay analysis.

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?

No information is provided about when to use this tool versus alternatives, prerequisites, or data preparation. It does not compare itself to sibling tools or mention any exclusions, leaving the agent without guidance on selecting it over related statistical tools.

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