trace_chemical_on_draft

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds the matching mechanism (each KE matched to candidate assays) but says nothing about cost, latency, or what happens when a chemical matches no assay, and output schema handles returns.

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 sentence with the core action front-loaded and no filler. It is dense but appropriately sized for the operation.

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?

The output schema covers the return value and annotations cover safety, but for an 8-parameter tool with zero schema descriptions, the definition omits identifier-selection rules and threshold semantics that an agent needs to invoke it correctly.

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 8 parameters, so the description must compensate and does not. It never explains that cas/name/dtxsid/inchikey are alternative chemical identifiers, nor what version_id, assay_limit (default 10, max 25), or min_hitcall (default 0.9) control.

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?

States a specific verb ('Project') and a specific resource ('one chemical's CompTox bioactivity onto draft key events'), including the intermediate step of matching KEs to candidate assays. It is distinguishable from siblings like map_chemical_to_aops, though the phrase 'draft graph activity overlay' is jargon-heavy.

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 indication of when to use this versus map_chemical_to_aops, search_assays_for_key_event, or get_evidence_matrix, nor any prerequisite (e.g., a draft must exist). The choice among four chemical identifier parameters is left entirely unguided.

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