mapping_provenance

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

No annotations are present, so the description bears full responsibility for behavioral disclosure. It clearly states that the tool writes multiple TSV files, indicating a write operation. However, it does not mention permissions, reversibility, or side effects beyond file creation, which is acceptable given the file-writing nature.

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, dense sentence that packs several key points (provenance, logic, unmapped, origin buckets) but becomes somewhat run-on. It could be more concise by splitting into bullet points or separate sentences for readability without losing content.

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 complexity of the tool (multiple output files, detailed logic), the description provides a thorough overview of what is produced and the concept of provenance. However, it omits parameter explanations, which reduces completeness slightly. With no output schema, listing output files is valuable.

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 input schema has 0% description coverage, meaning the description does not explain the parameters 'export' and 'workdir'. The description focuses entirely on outputs and logic, leaving parameter semantics undefined. This forces agents to rely solely on the schema, which lacks descriptions.

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 purpose: recovering provenance for KEGG/HMDB mappings beyond the initial pass, detailing logic, unmapped entries, and origin buckets. It lists specific output files, making the purpose concrete and distinct from sibling tools, which likely handle other aspects of metabolomics 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?

The description lacks explicit guidance on when to use this tool versus alternatives. It does not mention prerequisites, conditions, or when not to use it. The context is implied by the description but no direct usage recommendations are provided.

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