combine_versioned_exports

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

With no annotations, the description carries the full burden and does disclose meaningful behavior: it prepares a plan rather than downloading/combining, and it treats later-added variables as structurally missing in earlier versions. However, it omits side effects, whether the plan is returned or written to output_dir, and any required permissions.

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 front-loads the core action and scope before adding the version-missingness detail. Every phrase contributes semantic value with no filler.

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 a required path array and an output_dir, yet neither is described, and there is no output schema or return-value description. The description conveys the concept but leaves out the operational details an agent needs to invoke it confidently.

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% and the description adds no meaning for either parameter. 'Already downloaded exports' weakly implies export_paths, but output_dir is completely unexplained, so the agent must guess or inspect further to call the tool correctly.

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 states a specific action ('Prepare a ... combine plan') on a specific resource ('already downloaded exports') and adds the version-aware behavior of treating later-added variables as structurally missing in earlier versions. This clearly contrasts with sibling export-and-combine tools, which still need to download exports first.

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?

'Already downloaded exports' gives the agent a clear precondition that separates this tool from export_and_combine_questionnaire_versions and export_and_combine_all_versions_all_formats. It does not explicitly name alternatives or add a when-not-to-use rule, but the context is specific enough to guide selection.

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