openvsp.batch_export

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

With no annotations, the description carries the full burden. It states 'without solving,' which is a meaningful behavioral trait (no computation), but it does not mention whether the operation is non-destructive, requires prior batch submission, or has any side effects. The description is minimal but not misleading.

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?

One sentence, ten words, front-loaded with the action and key constraint. No fluff; every word contributes to the purpose.

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?

Despite being a simple tool with one parameter and an output schema, the description omits critical details: what 'batch_directory' should contain, how the format (CSV vs JSON) is selected, and prerequisites (e.g., must a batch snapshot already exist?). The agent cannot reliably invoke the tool correctly without further clarification.

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 0% and the description does not explain what 'batch_directory' refers to, its expected format, or how it relates to the saved snapshot. For a single required parameter, the description adds no semantic value beyond the schema, which is insufficient.

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 uses a specific verb ('Export') with a clear resource ('saved batch snapshot') and output format ('CSV/JSON'), plus a distinguishing condition ('without solving'). This clearly differentiates it from siblings like batch_submit, batch_status, and batch_cancel.

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?

It implies usage for exporting a saved batch, but does not explicitly state when to use it over alternatives like read_results or query. The phrase 'without solving' hints at a read-only operation but gives no conditions or exclusions, leaving the agent to infer the appropriate context.

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