file.export

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

With no annotations provided, the description carries full burden for behavioral disclosure. 'Export' implies a read operation that outputs data, but it doesn't specify what 'workflow' refers to (current active workflow? selected workflow?), whether it requires permissions, what the JSON structure contains, or if it's destructive to any state. This leaves significant gaps for a tool with mutation-like implications.

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, efficient sentence with no wasted words. It's front-loaded with the core action and resource, making it immediately understandable. Every word earns its place.

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 complexity of exporting a workflow (which could involve structured data) and the absence of both annotations and an output schema, the description is incomplete. It doesn't explain what 'workflow' means in context, what the JSON output contains, or any behavioral aspects. For a data export tool with no structured output documentation, this is inadequate.

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?

The tool has 0 parameters with 100% schema description coverage, so the schema fully documents the lack of inputs. The description doesn't need to add parameter details, and it correctly implies no required inputs for a simple export operation. A baseline of 4 is appropriate for zero-parameter tools.

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 'Export workflow to JSON' clearly states the verb ('Export') and resource ('workflow'), specifying the output format ('JSON'). It distinguishes from siblings like 'file.save' by focusing on export rather than general saving. However, it doesn't explicitly differentiate from other potential export tools that might exist.

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 no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., needing an active workflow), exclusions, or comparisons to sibling tools like 'workflow.getStructure' that might retrieve workflow data differently.

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