bag_health_mcp__download_export

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

Beyond annotations (read-only, idempotent, non-destructive), the description adds useful context: files are updated weekly, preview truncated at 3000 chars, and the output is raw data content.

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 well-organized with tags for use_case and important_notes, but contains some redundancy (e.g., 'Useful for bulk analysis' and use_case tag). Could be slightly more concise.

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?

Covers all necessary aspects: purpose, prerequisites (list_export_files), format options, limitations (preview truncation), and example. Output schema exists, so return value details are not needed.

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 already describes both parameters well, but the description reinforces with an example and clarifies the format default. The use_case tag adds context 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 it downloads a complete export dataset as CSV or JSON for a specific disease file, distinguishing it from siblings like list_export_files and get_disease_data by specifying the use case of bulk 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?

Explicitly guides when to use ('useful for bulk analysis', 'retrieve full raw dataset for offline analysis') and when not ('for very large datasets use IDD web interface'). Also directs to use bag_health_mcp__list_export_files to get valid file names.

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