lenx_export_task_data

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

No annotations are provided, so the description carries full burden. It discloses that results are sent to an email address, indicating asynchronous behavior beyond typical synchronous returns. This adds key behavioral context, though it omits potential side effects like rate limits or delays.

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 two sentences, directly stating the core function and delivery method. No extraneous information, efficient and front-loaded.

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?

Given the tool's 12 parameters and no output schema, the description adequately explains the primary action and result. It covers the export format and delivery mechanism, though it does not mention constraints like file size limits or processing time.

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?

With 100% schema description coverage, the baseline is 3. The description mentions 'CSV or XLSX' and 'specified email address', aligning with file_format and email parameters, but adds no further semantic meaning 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 tool exports task post data as CSV or XLSX and sends it via email. The verb 'request' is appropriate, and it distinguishes itself from sibling tools like lenx_get_task_data by specifying the export-and-email delivery method.

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 implies usage for exporting and emailing but lacks explicit guidance on when to use this tool versus alternatives like lenx_get_task_data. No exclusions or conditions are provided, so the agent must infer context.

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