generate_cochrane_report

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

With no annotations, the description carries the full burden of disclosing behavior, but it only says 'generate'. It does not mention that a file is written to output_path, whether existing files are overwritten, or any side effects. The scope of 'comprehensive' remains undefined.

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 concise sentence front-loaded with the verb and object. Every word adds value, with no filler or repetition of schema details.

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 tool has four parameters including a nested object, but the description gives no context on workflow positioning, expected report structure, or output behavior. The absence of an output schema makes the description the only narrative source, and it is too sparse to fully orient an agent.

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 100% coverage with descriptions for all four parameters, so baseline is 3. The description adds slight value by noting the report is in Cochrane format and mentions HTML/PDF, which aligns with the format enum, but it does not enrich the meaning of analysis_results or output_path beyond the schema.

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 action (generate), the object (comprehensive meta-analysis report), and the format (Cochrane format, HTML/PDF). It is distinct from sibling tools like perform_meta_analysis or generate_forest_plot, which cover other stages of the workflow.

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 guidance is provided on when to use this tool versus siblings. It does not mention prerequisites (e.g., meta-analysis results must be ready) or exclude use for tasks like plotting or validation. The intended context is implied only by the name and sibling list.

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