execute_export

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

No annotations are provided, so the description carries the full burden. It discloses the safety mechanism requiring confirmation=true, which adds transparency. However, it does not describe potential side effects, return values, or error handling. For a execute tool, some behavioral details are missing.

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 only two sentences, with the first sentence stating the core purpose and the second adding a critical usage note. It is front-loaded, efficient, and contains no unnecessary words.

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 simplicity (two parameters, no output schema, no annotations), the description is fairly complete. It covers what the tool does, how to invoke it (with confirmation=true), and the source of the command. It could mention what happens after execution (e.g., file output), but the description is adequate for an AI agent to use it correctly.

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?

Both parameters are documented in the schema (100% coverage). The description adds value by explaining that the 'command' parameter should be the exact output from preview_export_command and that 'confirmation' must be true. This provides additional context 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 it executes a previously previewed FastBCP export command. The verb 'execute' and resource 'FastBCP export command' are specific. It distinguishes from the sibling tool 'preview_export_command' by implying this is the actual execution step.

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 provides explicit guidance: it must be used after preview, and the confirmation parameter must be set to true. It does not explicitly state when not to use it or list alternatives, but the safety mechanism note is helpful. The prerequisite of having run preview is implied.

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