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

With no annotations, the description carries the burden and does so well: it declares that concentration_unit is REQUIRED, that there is deliberately no default, that a wrong choice shifts results by 1000x, and that the response echoes the unit and flags implausible profiles in unit_check. It omits any statement about auth/api_key handling or result structure beyond unit_check.

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-loads the purpose, then devotes its space to the one genuinely dangerous parameter. The unit paragraph is longer than strictly necessary but every sentence addresses a real failure mode, so it earns its place.

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 6-required-parameter tool with zero schema descriptions, the definition leaves most inputs unexplained. The output schema spares it from describing return values, but the missing explanation of timepoints/absorbances encoding and calibration inputs is a substantive gap an agent must guess around.

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% across 9 parameters, yet the description explains only concentration_unit thoroughly (plus a passing mention of reference_profile and the 900 mL default). The formats of timepoints and absorbances — critical string inputs — and the roles of calibration_slope/intercept and label_claim_mg are left entirely undocumented.

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 opening sentence gives a specific verb+resource+input domain: 'Calculate dissolution profile from UV-Vis absorbance time series.' That clearly separates it from generic siblings like covauv_quantify or covauv_validate, though it never names an alternative tool to contrast against.

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 concrete conditional usage for the f2 calculation ('Optionally calculates f2 similarity if reference_profile is provided') and strong guidance on when the unit choice matters. It stops short of saying when to prefer this tool over covauv_quantify or covauv_auto_analyze.

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