Export Extraction Result

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

With no annotations provided, the description fails to disclose behavioral details such as how the file is saved (local path vs. download), whether it overwrites existing files, or the nature of the return value. The only added context is 'latest,' which is minimal. This is a significant gap for an export tool.

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?

A single, grammatically complete sentence communicates the core function with no filler or redundancy. Perfectly 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?

The description is inadequate for a tool that triggers a file export. It does not address file destination, overwrite behavior, response format, or error conditions. The presence of an output schema is not leveraged in the description, and the minimal wording leaves the agent without sufficient context.

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 only restates the source options ('table/form/text') without explaining format implications, file naming, or how 'latest' is determined. The enums are self-explanatory, but the description does not compensate for the lack of schema documentation in prose.

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 'Export' as a specific verb and identifies the resource as 'latest table/form/text extraction,' clearly distinguishing it from extraction tools like extract_table or extract_text. It states the action and target unambiguously.

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 establishes clear usage context: it exports the most recent extraction result to a file. While it does not explicitly mention alternatives, none of the sibling tools perform export functionality, so the intended use is clear. It lacks explicit when-not or prerequisite guidance, but the context is sufficient for a 4.

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