export_and_combine_questionnaire_versions

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

With no annotations, the description carries the full burden. It does disclose the side effect of starting exports and clarifies that the result is a plan plus pending download steps rather than completed downloads. However, it omits details such as whether exports run asynchronously, how partial failures are handled, or what the returned combine plan actually contains.

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 that front-loads the core behavior. It is efficient, though its brevity leaves important semantic gaps.

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?

This is a high-level workflow with five parameters, no output schema, and no annotations, so the description must carry more weight. One sentence does not tell an agent what the combine plan looks like, how to perform the pending download steps, or what the parameters control.

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 does not compensate for any parameter. None of profile, output_dir, export_type, interview_status, or questionnaire_id_or_title are explained beyond the bare schema properties.

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 identifies a workflow that starts exports for all versions and returns a combine plan plus pending download steps. This is specific enough to convey the tool's function, though it does not explicitly differentiate itself from close siblings like export_all_questionnaire_versions or export_and_combine_all_versions_all_formats.

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 gives no guidance on when to use this tool instead of related alternatives. It does not mention prerequisites, or contrast itself with export_all_questionnaire_versions, combine_versioned_exports, or export_and_combine_all_versions_all_formats.

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