import_revman_data

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

No annotations are provided, so the description carries the behavioral disclosure burden. It describes the parsing/extraction behavior and mentions adherence to 'Cochrane standards,' which adds context. However, it does not disclose side effects (e.g., whether data is persisted), permission requirements, or error handling behavior, leaving some ambiguity for an import tool.

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 exactly two sentences, front-loaded with the main action, and every word provides useful information. There is no redundancy or filler, making it highly concise while covering the essentials.

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 simplicity (2 params, no output schema) and lack of annotations, the description is moderately complete. It explains what data is parsed and extracted, but it does not clarify whether the tool returns a dataset, stores data, or requires any external context. For a tool likely used as the first step in a workflow, this leaves some ambiguity about its output or side effects.

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 coverage is 100%: both 'file_path' and 'format' have clear descriptions in the schema. The tool description adds context about supported data structures ('structured Cochrane datasets and flat record arrays') but does not add meaning to individual parameters beyond the schema, so the baseline 3 is appropriate.

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 ('Import and parse') and resource ('meta-analysis data'), and explicitly lists supported formats. It is well differentiated from sibling tools (validate, analyze, plot, bias, report), which focus on later workflow stages.

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?

Usage context is implied — it is the data ingestion step before validation and analysis — but the description does not explicitly state when to use it over alternatives or when not to use it. The mention of 'structured Cochrane datasets and flat record arrays' provides some applicability guidance, but no direct exclusions or alternative references.

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