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

With no annotations at all, the description carries the full burden, and it does disclose meaningful behavior: each match includes the published volume, a verbatim quote that has been verified against the protocol text, both reagents' share, and a within-20% agreement verdict. It does not state that the operation is read-only, what happens when no kit match or no quote is found, how many matches are returned, or that an LLM (Muse Spark) reads the protocols, implying possible latency or cost.

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 a single dense, run-on sentence with a colon-delimited list, so the enumeration of match fields is not easy to scan. Every element is substantive, but the phrasing ("next to those of", "read by Muse Spark") front-loads awkwardly rather than stating the core action first.

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?

There is no output schema and no annotations, so the description must do all the work; it does a decent job describing the returned match structure and tolerance check, but leaves the sole parameter's meaning and the tool's usage context unexplained for what appears to be a non-trivial cross-referencing operation.

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?

The schema has one required parameter, "name", with 0% description coverage, and the description never explains it. "This run's" weakly hints that the name identifies a run, but it could equally be a kit or protocol name; the description should have resolved this ambiguity since the schema does not.

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 names a specific operation: comparing this run's per-reaction volumes against published protocols.io protocols using the same kit, and enumerating what each match contains. It is clearly not get_run, get_related_protocols or get_protocol, though it never explicitly says how it differs from get_related_protocols, which also deals with linked published protocols.

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 when-to-use or when-not-to-use guidance, no prerequisites, and no mention of sibling tools. The agent must infer that this is a post-run validation step; the description is entirely about result content rather than invocation context.

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